Re: [patch] O(1) scheduler, -G1, 2.5.2-pre10, 2.4.17 (fwd)

["François Cami" <stilgar2k@wanadoo.fr>]

Robert Love wrote:

> On Fri, 2002-01-11 at 16:46, Timothy Covell wrote:
> 
>> But, given the above case, what happens when you have Sendmail on
>> the first CPU and Squid is sharing the second CPU?  This is not optimal
>> either, or am I missing something?
> 
> Correct.  I sort of took the "optimal cache use" comment as 
> tongue-in-cheek.  If I am mistaken, correct me, but here is my 
> perception of the scenario:
> 
> 2 CPUs, 3 tasks.  1 task receives 100% of the CPU time on one CPU.  The 
> remaining two tasks share the second CPU.  The result is, of three 
> evenly prioritized tasks, one receives double as much CPU time as the 
> others.


Yes, but that makes sense if the one that receives double as much
CPU time as the others _needs_ that CPU time. For example, an idle
MTA _should_ not receive as much CPU time as an overworked proxy
server... Yet, unless someone changes the priority, they are treated
evenly by the scheduler. This is not so good in my mind.


> Aside from the cache utilization, this is not really "fair" -- the 
> problem is, the current design of load_balance (which is quite good) 
> just won't throw the tasks around so readily.  What could be done -- 
> cleanly -- to make this better?
> 
> 	Robert Love


Is it possible for the scheduler to take into account another parameter
than priority to decide an app' CPU affinity ? For example, size
in memory and %CPU. For example, if an app accounts for
80% of the total CPU utilisation, by all means it should stay
on the same CPU. That, in my mind, would have the effect that this
app would run faster (because of the cache) AND that the load on
the machine would decrease (having to bump that app from one
CPU to another is _not_ good).

Is this feasible, or am I dreaming ?

François Cami