Date: Tue, 30 Mar 2004 06:26:12 +0100 From: "Niall Douglas" <s_sourceforge@nedprod.com> To: freebsd-threads@freebsd.org Subject: Re: GDB 6.0 and FreeBSD threads Message-ID: <40691304.15123.69C3765@localhost> In-Reply-To: <Pine.GSO.4.10.10403292233000.12734-100000@pcnet5.pcnet.com> References: <4068DA49.24401.5BE9BE4@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29 Mar 2004 at 22:38, Daniel Eischen wrote: > > > Why not just run all threads SCOPE_PROCESS? Then the system will > > > do that for you. > > > > The pthreads implementations I've seen won't utilise more than one > > processor unless it's SCOPE_SYSTEM. The obviates the reason most > > people use threads, hence the success of the 1:1 model which is a > > very blunt axe. > > That's untrue for libpthread. It creates automatically creates one > KSE for each CPU. You can increase the number of CPUs by setting > sysctls kern.threads.debug=1 and raising kern.threads.virtual_cpu. It > also respects pthread_setconcurrency, but you're limited to > kern.threads.virtual_cpu. Yes, all process scope threads run in these > KSES. My apologies if this is a question already answered many times previously - what's then the difference between specifying SCOPE_SYSTEM and SCOPE_PROCESS on libpthread? Is it basically whether the thread competes with all threads or just with threads within its process for that process' time slice? Cheers, Niall -----BEGIN PGP SIGNATURE----- Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2 iQA/AwUBQGkE9MEcvDLFGKbPEQJZawCfRWCdhRQsGw9w68NA1UvhmjEQPm8AoOG+ JCTA4487OHDzXKt792tbC6q5 =cabR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40691304.15123.69C3765>