Message195360
| Author | pitrou |
|---|---|
| Recipients | christian.heimes, hynek, jcea, neologix, pitrou, tarek, vstinner |
| Date | 2013-08-16.16:48:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1376671703.2510.3.camel@fsol> |
| In-reply-to | <520E56B2.70209@cheimes.de> |
| Content | |
|---|---|
> Am 16.08.2013 18:24, schrieb Charles-François Natali: > > Well, first we'll have to make the code thread-safe, if we want to > > keep a persistent FD open. Which means we'll have to add a lock, which > > is likely to reduce concurrency, and overall throughput. > > Why locking? /dev/urandom is a pseudo char device. You can have multiple > readers on the same fd without any locking. You must put a lock around the open() call, though, to avoid calling it several times and losing an fd. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-16 16:48:31 | pitrou | set | recipients: + pitrou, jcea, vstinner, christian.heimes, tarek, neologix, hynek |
| 2013-08-16 16:48:31 | pitrou | link | issue18756 messages |
| 2013-08-16 16:48:31 | pitrou | create | |