Date: Wed, 23 May 2007 16:33:50 -0700 (PDT) From: Jeff Roberson <jroberson@chesapeake.net> To: Marcel Moolenaar <xcllnt@mac.com> Cc: arch@freebsd.org Subject: Re: sched_lock && thread_lock() Message-ID: <20070523163109.X9443@10.0.0.1> In-Reply-To: <6A9BD12D-D93C-4AE8-B4F4-D59A0327032D@mac.com> References: <20070520155103.K632@10.0.0.1> <20070523155236.U9443@10.0.0.1> <6A9BD12D-D93C-4AE8-B4F4-D59A0327032D@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 May 2007, Marcel Moolenaar wrote: > > On May 23, 2007, at 3:56 PM, Jeff Roberson wrote: > >> Resuming the original intent of this thread; >> >> http://www.chesapeake.net/~jroberson/threadlock.diff Woops! people.freebsd.org/~jeff/threadlock.diff > > 404 Not Found. > > The old patch was missing PowerPC & ia64. Will the final version > include those as well? There are a couple of uses of the global scheduler lock in some architecture specific locations. They will continue to be safe with the 4BSD scheduler. I intended to work on these issues with the architecture maintainers after the threadlock patch goes in. Can you suggest some alternative to sched_lock for pmap_switch in ia64? There are a couple of these small issues that should be perfectly safe that I was hoping to address outside of this patch so that it didn't get too big. Jeff > > -- > Marcel Moolenaar > xcllnt@mac.com > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070523163109.X9443>