linux-kernel - Re: [PATCH 1/2] Customize sched domain via cpuset

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: <1207050968.8514.721.camel@twins>
Date:	Tue, 01 Apr 2008 13:56:08 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Paul Jackson <pj@....com>
Subject: Re: [PATCH 1/2] Customize sched domain via cpuset

On Tue, 2008-04-01 at 13:40 +0200, Andi Kleen wrote:
> Hidetoshi Seto <seto.hidetoshi@...fujitsu.com> writes:
> 
> > Using cpuset, now we can partition the system into multiple sched domains.
> > Then, how about providing different characteristics for each domains?
> 
> Did you actually see much improvement in any relevant workload
> from tweaking these parameters?  If yes what did you change?
> And how much did it gain?
> 
> Ideally the kernel should perform well without much tweaking
> out of the box, simply because most users won't tweak. Adding a 
> lot of such parameters would imply giving up on good defaults which 
> is not a good thing.

>>From what I understand they need very aggressive idle balancing; much
more so than what is normally healty.

I can see how something like that can be useful when you have a lot of
very short running tasks. These could pile up on a few cpus and leave
others idle.


--
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/