From: Tejun Heo <tj@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
svaidy@linux.vnet.ibm.com, nacc@linux.vnet.ibm.com,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
lizefan@huawei.com, anton@samba.org, bharata@linux.vnet.ibm.com,
cgroups@vger.kernel.org, paulmck@linux.vnet.ibm.com,
mingo@kernel.org
Subject: Re: [PATCH V2] cpuset: Add knob to make allowed masks hotplug invariant on legacy hierarchy
Date: Wed, 15 Apr 2015 11:48:02 -0400 [thread overview]
Message-ID: <20150415154802.GB30337@htj.duckdns.org> (raw)
In-Reply-To: <20150415153035.GA25390@mail.hallyn.com>
On Wed, Apr 15, 2015 at 10:30:35AM -0500, Serge E. Hallyn wrote:
> On Wed, Apr 15, 2015 at 05:19:26PM +0200, Peter Zijlstra wrote:
> > On Wed, Apr 15, 2015 at 10:03:02AM -0500, Serge E. Hallyn wrote:
> >
> > > Peter, is the question "why can't we just use the unified hierarchy for
> > > cpusets"?
> >
> > No, the question is why can't you use the unified hierarchy cpuset
> > semantics -- without the actual unified hierarchy stuff.
>
> Ok - that I don't know the answer to. Does sound like it would
> simplify things, reduce # of sets of semantics.
What'd be the reason for not using the unified hierarchy tho? The
adaptable required isn't that big and the patchset already proposes
significant amount of behavior change. Sure it'd be a bit more hassle
but does that really justify introducing yet another operation mode?
This is why unified hierarchy is being added in the first place. One
can argue "but *I* just need this specific part changed" but allowing
combinations of all those little variations is gonna lead us to a
hellish place.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-04-15 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 14:11 Preeti U Murthy
2015-04-11 8:35 ` Peter Zijlstra
2015-04-11 11:21 ` Preeti U Murthy
2015-04-11 13:42 ` Peter Zijlstra
2015-04-13 7:01 ` Peter Zijlstra
2015-04-13 8:25 ` Preeti U Murthy
2015-04-13 12:16 ` Preeti U Murthy
2015-04-13 14:43 ` Peter Zijlstra
2015-04-15 11:40 ` Preeti U Murthy
2015-04-15 15:03 ` Serge E. Hallyn
2015-04-15 15:19 ` Peter Zijlstra
2015-04-15 15:30 ` Serge E. Hallyn
2015-04-15 15:48 ` Tejun Heo [this message]
2015-04-15 16:15 ` Serge E. Hallyn
2015-04-15 16:18 ` Tejun Heo
2015-04-15 16:36 ` Serge E. Hallyn
2015-04-16 11:57 ` Preeti U Murthy
2015-04-20 3:28 ` Zefan Li
2015-04-13 14:50 ` Tejun Heo
2015-04-13 15:05 ` Peter Zijlstra
2015-04-15 11:12 ` Preeti U Murthy
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=20150415154802.GB30337@htj.duckdns.org \
--to=tj@kernel.org \
--cc=anton@samba.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=serge@hallyn.com \
--cc=svaidy@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®