Date: Sat, 26 Aug 2006 13:43:48 +1100 From: Andrew MacIntyre <andymac@bullseye.apana.org.au> To: freebsd-stable@freebsd.org Subject: Re: [AMD64-SMP] I can't get my cpus working at 100% Message-ID: <44EFB564.8090004@bullseye.andymac.org> In-Reply-To: <14989d6e0608241410n2b8a5fdwe98a927dea91be40@mail.gmail.com> References: <e92de5ef0608241109x2aa5b79u32a4e304d34f29d5@mail.gmail.com> <20060824190651.GA49364@xor.obsecurity.org> <14989d6e0608241410n2b8a5fdwe98a927dea91be40@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Walther wrote:
> A nice example of a program being able to do threading, but one CPU
> (core) only is python.
This is not strictly correct: Python relies on a global interpreter lock
(aka GIL) to protect internal data structures. When code in the Python
process doesn't require access to these data structures, threads can run
outside the influence of the lock and run simultaneously on multiple
CPUs. Python's I/O system (eg file/network I/O) and many Python
extensions do exactly this.
--
-------------------------------------------------------------------------
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370
andymac@pcug.org.au (alt) | Belconnen ACT 2616
Web: http://www.andymac.org/ | Australia
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44EFB564.8090004>