➜

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.

作者 christian.heimes
收信人 christian.heimes, hynek, jcea, neologix, pitrou, tarek, vstinner
日期 2013-08-16.16:43:31
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <520E56B2.70209@cheimes.de>
In-reply-to <CAH_1eM0dFWCCmoi6tZW6U1eJJ-AL-TKFu6J0LjPkGrbZpwPqXQ@mail.gmail.com>
内容
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?
历史
日期 用户 动作 参数
2013-08-16 16:43:31christian.heimes修改recipients: + christian.heimes, jcea, pitrou, vstinner, tarek, neologix, hynek
2013-08-16 16:43:31christian.heimes链接issue18756 messages
2013-08-16 16:43:31christian.heimes创建