From: Peter Zijlstra <peterz@infradead.org>
To: Dave Hansen <dave@sr71.net>
Cc: mingo@kernel.org, hpa@linux.intel.com, brice.goglin@gmail.com,
bp@alien8.de, linux-kernel@vger.kernel.org,
dave.hansen@linux.intel.com
Subject: Re: [RFC][PATCH 6/6] sched: consolidate config options
Date: Sat, 20 Sep 2014 01:03:08 +0200 [thread overview]
Message-ID: <20140919230308.GK2832@worktop.localdomain> (raw)
In-Reply-To: <541C80E1.9040601@sr71.net>
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.
next prev parent reply other threads:[~2014-09-19 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 22:33 [RFC][PATCH 0/6] fix topology for multi-NUMA-node CPUs Dave Hansen
2014-09-17 22:33 ` [RFC][PATCH 1/6] topology: rename topology_core_cpumask() to topology_package_cpumask() Dave Hansen
2014-09-17 22:33 ` [RFC][PATCH 2/6] x86: introduce cpumask specifically for the package Dave Hansen
2014-09-18 14:57 ` Peter Zijlstra
2014-09-17 22:33 ` [RFC][PATCH 3/6] x86: use package_map instead of core_map for sysfs Dave Hansen
2014-09-17 22:33 ` [RFC][PATCH 4/6] sched: eliminate "DIE" domain level when NUMA present Dave Hansen
2014-09-18 17:28 ` Peter Zijlstra
2014-09-17 22:33 ` [RFC][PATCH 5/6] sched: keep MC domain from crossing nodes OR packages Dave Hansen
2014-09-17 22:33 ` [RFC][PATCH 6/6] sched: consolidate config options Dave Hansen
2014-09-18 17:29 ` Peter Zijlstra
2014-09-19 19:15 ` Dave Hansen
2014-09-19 23:03 ` Peter Zijlstra [this message]
2014-09-18 7:45 ` [RFC][PATCH 0/6] fix topology for multi-NUMA-node CPUs Borislav Petkov
[not found] ` <CAOjmkp8EGO0jicmdO=p6ATHz-hUJmWb+xoBLjOdLBUwwGzyhhg@mail.gmail.com>
2014-09-22 15:54 ` Aravind Gopalakrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140919230308.GK2832@worktop.localdomain \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=brice.goglin@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox