Date: Sun, 8 Oct 2006 15:59:59 -0700 (PDT) From: Kip Macy <kmacy@fsmware.com> To: Attilio Rao <attilio@freebsd.org> Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-current@freebsd.org, David Xu <davidxu@freebsd.org>, Ivan Voras <ivoras@fer.hr> Subject: Re: [PATCH] MAXCPU alterable in kernel config - needs testers Message-ID: <20061008155817.G29803@demos.bsdclusters.com> In-Reply-To: <3bbf2fe10610081555r67265368sf7f12edbf35bff0d@mail.gmail.com> References: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com> <20061008135031.G83537@demos.bsdclusters.com> <4529667D.8070108@fer.hr> <200610090634.31297.davidxu@freebsd.org> <20061008225150.GK793@funkthat.com> <3bbf2fe10610081555r67265368sf7f12edbf35bff0d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > How would you see a sched_lock decomposition (and, if it is possible, > how many locks it could be decomposed in?) Rather than having a per thread lock, Solaris uses the lock for the current container that a thread is associated with (cpu, run queue, sleep queue, etc.) to serialize thread updates. I think this is probably the best approach. A per proess spin lock would not scale well for large multi-threaded apps. -Kip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061008155817.G29803>