Date: Mon, 4 Jun 2007 18:17:25 -0700 (PDT) From: youshi10@u.washington.edu To: current@freebsd.org Subject: Re: HEADS UP: threadlock going in, likely tonight. Message-ID: <Pine.LNX.4.43.0706041817250.27541@hymn02.u.washington.edu> In-Reply-To: <20070604170715.S606@10.0.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Jun 2007, Jeff Roberson wrote:
> Ok folks, make sure you don't sup a snapshot from the middle of my commits
> and you should have a solid working tree.
>
> I am going to work on the version of ule with per-cpu locks (sched_smp) a
> little while longer before sending that out again. I suspect this will address
> many of the scheduling related complaints and performance problems people have
> had.
>
> Thanks,
> Jeff
>
> On Mon, 4 Jun 2007, Jeff Roberson wrote:
>
>> I will now begin committing threadlock.
>>
>> Please wait to cvsup until I send another mail.
>>
>> Thanks,
>> Jeff
>>
>> On Mon, 4 Jun 2007, Jeff Roberson wrote:
>>
>>> This has been up for review and testing for some time. I think it's ready
>>> for prime-time. Only one new bug came up over the weekend and I believe I
>>> have that fixed.
>>>
>>> I'm going to commit the patch in stages but the tree will not be
>>> functional in between. I'm not able to break it down into several
>>> functional steps but I want to leave meaningful commit messages in several
>>> files.
>>>
>>> I will send out one more mail when I start and another when I'm done.
>>>
>>> Thanks,
>>> Jeff
Jeff,
Thanks again and I'll be sure to burn in the new scheduling prio system on my desktop :).
Cheers,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.43.0706041817250.27541>