Message129966
| Author |
pitrou |
| Recipients |
amaury.forgeotdarc, eric.smith, neologix, pitrou |
| Date |
2011年03月03日.13:09:11 |
| SpamBayes Score |
8.013036e-07 |
| Marked as misclassified |
No |
| Message-id |
<1299157748.3773.2.camel@localhost.localdomain> |
| In-reply-to |
<1299157148.89.0.97600358972.issue11382@psf.upfronthosting.co.za> |
| Content |
> Just to be clear, I'm not at all criticizing the current GIL
> implementation, there's been a great work done on it.
> I'm just saying that releasing and re-acquiring the GIL around fast
> syscalls is probaly not a good idea.
If these syscalls aren't likely to yield control to another thread, then
I agree there's no point in releasing the GIL around them.
(but is it the case that they are always fast? for example, how about
dup() on a network file system? or is it indifferent?) |
|