Date: Thu, 16 Jun 2005 06:07:38 +0800 From: David Xu <davidxu@freebsd.org> To: Jiawei Ye <leafy7382@gmail.com> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Robert Watson <rwatson@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libthr libthr.3 Message-ID: <42B0A6AA.6050501@freebsd.org> In-Reply-To: <c21e92e205061513044b672a3a@mail.gmail.com> References: <200506151521.j5FFLA0A003330@repoman.freebsd.org> <c21e92e205061513044b672a3a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jiawei Ye wrote: >On 6/15/05, Robert Watson <rwatson@freebsd.org> wrote: > > >>rwatson 2005-06-15 15:21:10 UTC >> >> FreeBSD src repository >> >> Modified files: >> lib/libthr libthr.3 >> Log: >> Remove incorrect BUGS entry: libthr does support process-scope thread >> scheduling. >> >> >> >We still have this sysctl in -current: kern.threads.thr_scope. >According to Dan, this is only available to libthr, but in your commit >you mentioned that libthr does not support process-scope scheduling, >then what does the sysctl control in reality? The -d option displays >"sys or proc scope scheduling". > >Jiawei > > > libthr does support process scope and system scope thread, it is controllable by user code, the pthread_attr_setscope() can tune the scope, however kernel has a sysctl can override user setting, if thr_scope is zero, the thread scheduling scope is set by user code, if it is 1, kernel will force all threads to be process scope, if it is 2, all threads will be system scope, ignore user setting, I use it only for debugging purpose. David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B0A6AA.6050501>