From owner-p4-projects@FreeBSD.ORG  Wed Oct 27 19:53:02 2004
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 68BA616A4D0; Wed, 27 Oct 2004 19:53:02 +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 2A0C416A4CE; Wed, 27 Oct 2004 19:53:02 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F2E8A43D45; Wed, 27 Oct 2004 19:53:01 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id DCEDE7A427; Wed, 27 Oct 2004 12:53:01 -0700 (PDT)
Message-ID: <417FFC9D.1080500@elischer.org>
Date: Wed, 27 Oct 2004 12:53:01 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <200410271747.i9RHlpjg005855@repoman.freebsd.org>
In-Reply-To: <200410271747.i9RHlpjg005855@repoman.freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: Perforce Change Reviews <perforce@freebsd.org>
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 <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2004 19:53:03 -0000



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"