Message 195356 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	christian.heimes
Recipients	christian.heimes, hynek, jcea, neologix, pitrou, tarek, vstinner
Date	2013-08-16.16:43:31
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<520E56B2.70209@cheimes.de>
In-reply-to	<CAH_1eM0dFWCCmoi6tZW6U1eJJ-AL-TKFu6J0LjPkGrbZpwPqXQ@mail.gmail.com>

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. Did you know that Java keeps one persistent fd to /dev/urandom?

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. Did you know that Java keeps
one persistent fd to /dev/urandom?

History
Date	User	Action	Args
2013-08-16 16:43:31	christian.heimes	set	recipients: + christian.heimes, jcea, pitrou, vstinner, tarek, neologix, hynek
2013-08-16 16:43:31	christian.heimes	link	issue18756 messages
2013-08-16 16:43:31	christian.heimes	create