470,612 Members | 2,316 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,612 developers. It's quick & easy.

global interpreter lock

I just need confirmation that I think right.

Is the files thread_xxx.h (xxx = nt, os2 or whatever) responsible for
the
global interpreter lock in a multithreaded environment?

I'm currently writing my own thread_VW for VxWorks, thats why I'm
asking.

//Tommy

Oct 18 '05 #1
2 1380
To**********@gmail.com wrote:
I just need confirmation that I think right.

Is the files thread_xxx.h (xxx = nt, os2 or whatever) responsible for
the
global interpreter lock in a multithreaded environment?

I'm currently writing my own thread_VW for VxWorks, thats why I'm
asking.

//Tommy

Someone can correct me if I'm wrong, but the lock actually lives in
ceval.c, around here:

802 PyThread_release_lock(interpreter_lock);
803
804 /* Other threads may run now */
805
806 PyThread_acquire_lock(interpreter_lock, 1);
This was taken from what appears to be a 2.4.1 release rather than a CVS
checkout. It looks like the PyThread_type_lock is defined in the
thread_xxx.h files, though.

HTH,

- jmj
Oct 18 '05 #2
Thanks,
PyThread_release_lock() is implemented in all thread_xxx.h files.

So I thought right but specified my question like a stupid ;)

//T

Oct 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Tomas Christiansen | last post: by
61 posts views Thread by km | last post: by
6 posts views Thread by martin | last post: by
41 posts views Thread by Miguel Dias Moura | last post: by
15 posts views Thread by randyr | last post: by
reply views Thread by Duncan Grisby | last post: by
10 posts views Thread by Janto Dreijer | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.