Message163179
| Author | pitrou |
|---|---|
| Recipients | kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner |
| Date | 2012-06-19.15:07:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1340118225.3361.11.camel@localhost.localdomain> |
| In-reply-to | <1340118156.3361.10.camel@localhost.localdomain> |
| Content | |
|---|---|
> > The implementation for multiprocessing.Condition is virtually the same > > as Listing 3 which the author says he thinks is "formally correct" but > > with "a fundamental performance problem". > > To me, it seems similar to the last listing (under "The Sequel—NT and > PThreads"): there's a separate semaphore per waiter, used to wake it up > when signal() or broadcast() is called. Ah, you said multiprocessing.Condition. Sorry. I was thinking about threading.Condition. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-06-19 15:07:05 | pitrou | set | recipients: + pitrou, loewis, paul.moore, kristjan.jonsson, vstinner, python-dev, sbt |
| 2012-06-19 15:07:04 | pitrou | link | issue15038 messages |
| 2012-06-19 15:07:04 | pitrou | create | |