Date: Wed, 23 Nov 2005 17:41:20 -0700 From: Scott Long <scottl@samsco.org> To: David Xu <davidxu@freebsd.org> Cc: current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: 4BSD process starvation during I/O Message-ID: <43850C30.4060801@samsco.org> In-Reply-To: <43850AB7.4000109@freebsd.org> References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051124000824.GA11032@xor.obsecurity.org> <43850AB7.4000109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David Xu wrote: > Kris Kennaway wrote: > >> On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: >> >> >>> Kris Kennaway wrote: >>> >>> >>> >>>> Perhaps this can be tweaked. >>>> >>>> Kris >>>> >>>> P.S. Please, no responses about how maybe someone could write a new >>>> scheduler that doesn't have this property. >>>> >>>> >>>> >>>> >>>> >>> >>> Can you try it again with FULL_PREEMPTION is turned on ? >>> >> >> >> Didn't really make a difference: >> >> >> > This might only can be fixed when msleep no longer explicitly fiddles > thread priority, let scheduler fully control it. > I don't agree. The more likely problem according Stephan is that threads returning from userland get their priority elevated so they have a better chance of running right away. If you have plans to change how tsleep and msleep manage priorities, please discuss it on arch@ before you start making changes. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43850C30.4060801>