Subject: Re: scheduler interactivity: timeslice calculation seem wrong
From: Eric St-Laurent <ericstl34@sympatico.ca>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <bhtt73$8i4$1@gatekeeper.tmr.com>
References: <3F41B43D.6000706@cyberone.com.au>
	 <1061276043.6974.33.camel@orbiter>  <bhtt73$8i4$1@gatekeeper.tmr.com>
Content-Type: text/plain
Message-Id: <1061337283.1123.8.camel@orbiter>
Mime-Version: 1.0
Date: Tue, 19 Aug 2003 19:54:43 -0400
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 647
Lines: 14

> This could go in 2.7, though, or possibly in 2.6.x depending on how the
> powers that be feel. I think having the scheduler as a plugin is a win
> in terms of having whole special-use algorithms. It would have to be
> done *very* carefully to be sure it didn't add measurable overhead.

Well i was thinking of a compile time or at best boot time selection. It
should not add any mesurable overhead.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/