linux-kernel - Re: [RFC][PATCH 6/6] sched: consolidate config options

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] [day] [month] [year] [list]

Message-ID: <20140919230308.GK2832@worktop.localdomain>
Date:	Sat, 20 Sep 2014 01:03:08 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Dave Hansen <dave@...1.net>
Cc:	mingo@...nel.org, hpa@...ux.intel.com, brice.goglin@...il.com,
	bp@...en8.de, linux-kernel@...r.kernel.org,
	dave.hansen@...ux.intel.com
Subject: Re: [RFC][PATCH 6/6] sched: consolidate config options

On Fri, Sep 19, 2014 at 12:15:45PM -0700, Dave Hansen wrote:
> On 09/18/2014 10:29 AM, Peter Zijlstra wrote:
> >> > +config SCHED_BOOK
> >> > +	def_bool y
> >> > +	prompt "Book scheduler support"
> >> > +	depends on ARCH_ENABLE_SCHED_BOOK
> >> > +	select SCHED_MC
> >> > +	help
> >> > +	  Book scheduler support improves the CPU scheduler's decision making
> >> > +	  when dealing with machines that have several books.
> >> > +
> >> > +	  Currenltly only used on s390 which has only a single NUMA node.
> >> > +	  Books are collections of CPUs that are grouped similarly to a NUMA
> >> > +	  node, but without the same memory properites that NUMA nodes have.
> > Nothing outside of s390 knows about SCHED_BOOK, it doesn't make sense to
> > have that here.
> 
> By sticking all of them together, my hope was that folks who were going
> to add a topology level could see all of the existing options in a
> single place.
> 
> But, just say the word and I'll yank it out and repost.

Yeah, I think its best to leave it a s390 private afair.
--
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/