linux-kernel - Re: Plumbers: Tweaking scheduler policy micro-conf RFP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANQmPXjiqtDE_4ZmNrtrb9qjB=gyv=NiPr3pdaHFirSs0T3ptQ@mail.gmail.com>
Date:	Tue, 22 May 2012 13:14:47 +0800
From:	Chen <hi3766691@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Vincent Guittot <vincent.guittot@...aro.org>,
	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, mou Chen <hi3766691@...il.com>
Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP

On Tue, May 22, 2012 at 10:38 AM, Chen <hi3766691@...il.com> wrote:
> Still you are just trying to said that your code is not bloated?
> Up to over 500K for a cpu scheduler. Laughing

So please stop increasing the size of cpu scheduler's code. Users
can't benefit anything from that. Also the interactivity problem of
scheduler is still exist though it improves a lot already.

It is better to stop bloating. Isn't ?

Also I m quite agree with Linus. The model of the scheduler now is
complex and there are many *UNNECESSARY* code. I CAN'T REALLY BENEFIT
ANYTHING. I just make my kernel with -j2 and the music is already
sucking![Intel E7500, 2.9GHZ, two core]. It can show that how the
interactivity problem is serious with mainline cpu scheduler. I know
it is not all the fault of mainline cpu scheduler but it is still a
big interactivity problem with it. [me think that Peter is proud of
his insane-box-supporting stuff]
--
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/