From owner-p4-projects@FreeBSD.ORG Wed Oct 27 20:35:06 2004 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 4A88116A4D3; Wed, 27 Oct 2004 20:35:06 +0000 (GMT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 255E416A4D1 for ; Wed, 27 Oct 2004 20:35:06 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 001B643D1D for ; Wed, 27 Oct 2004 20:35:05 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2486 invoked from network); 27 Oct 2004 20:35:05 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Oct 2004 20:35:05 -0000 Received: from [10.50.40.221] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i9RKYrMN022599; Wed, 27 Oct 2004 16:35:01 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Julian Elischer Date: Wed, 27 Oct 2004 16:31:16 -0400 User-Agent: KMail/1.6.2 References: <200410271747.i9RHlpjg005855@repoman.freebsd.org> <417FFC9D.1080500@elischer.org> In-Reply-To: <417FFC9D.1080500@elischer.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410271631.16160.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Perforce Change Reviews Subject: Re: PERFORCE change 63836 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 20:35:06 -0000 On Wednesday 27 October 2004 03:53 pm, Julian Elischer wrote: > John Baldwin wrote: > > on needresched? If so, it goes into sched_userret(). > >+- Need lots of thought on realtime and idle time priorities and handling > >+ tsleep() priority "boosts" for such processes. Might need to make > >+ the priority boost be something passsed to sched_sleep() rather than > >+ a sched_prio() call. > > I'd like to see the boost kept separate and added during the calcualtions > that way various algorythms could be used on the boost.. > for example I'd like to see the boost exponentially reduced each > clocktick encounterred in userspace > or maybe the boost could include a suggested lifetime.. > e.g. "boost by 10% for 20mSec" This would let the scheduler do that. Right now we just change the priority via sched_prio(). This change would instead tell the scheduler at sched_sleep() what the boost is and it is free to store it and use it however it wants. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org