[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANQmPXhQYnCn7b2fL_eBRf+QNPb4p2HLUZgcDs3VVeB51=6xpg@mail.gmail.com>
Date: Fri, 27 Apr 2012 16:25:58 +0800
From: mou Chen <hi3766691@...il.com>
To: Hillf Danton <dhillf@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] RIFS cpu scheduler
On Fri, Apr 27, 2012 at 4:10 PM, mou Chen <hi3766691@...il.com> wrote:
> On Tue, Apr 24, 2012 at 7:57 PM, Hillf Danton <dhillf@...il.com> wrote:
>> On Mon, Apr 23, 2012 at 9:38 PM, mou Chen <hi3766691@...il.com> wrote:
>>>
>>> The SMP code is the same.The algorithum is different. :-)
>>>
>> Then would you please share the output of?
>>
>> diff -pu bfs-version rifs-version
>
> No any string "bfs-version" was found.
>
> Also I have just finish rewriting the scheduler's code in a more
> readable way.For example changing goto need_resched to loop, dividing
> workqueue sleep checking in a individual function.
>
> I haven't post the newest code yet. :-(
>
> Chen
Also the thing I want to say is, do not try to increase the clock
frequency.It is a stubid way really and still still many guys think
that it is the way to decrease the latency. :-( Everyone knows that
the latency is measuring that the time needed for waking up a process.
For example, an interactive task sleeps 100ms, then when it continues
running, the process hasn't run for 120 ms on SCHED_A.The process
hasn't run for 101ms when it is running on a SHCED_B kernel and we
would say SCHED_B is more interactive than SCHED_A. So there is not
too much relation between latency and clock frequency.
RIFS is not using any fomula and the algorithum RIFS use is simple and
it works very well with make -j64.There is no lagging with firefox.
:-)
Chen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists