Subject: Re: Please Revert newlock2
To: None <firstname.lastname@example.org>
From: Bucky Katz <email@example.com>
Date: 02/20/2007 14:45:28
Jason Thorpe <firstname.lastname@example.org> writes:
> On Feb 18, 2007, at 7:32 AM, Thor Lancelot Simon wrote:
>> 2) Either cause them to perform acceptably for your application, or
>> endeavor to get M:N back in a supported state for uniprocessors.
> The issue is adapting the SA code to all of the new scheduling
> infrastructure that came along with newlock2. It's not a simple
I dunno. #ifdefing out the "new scheduling infrastructure" should be
just as easy as #ifdefing in the SA code.
Not seeing a problem here.