From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <longman@redhat.com>, Zefan Li <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ingo Molnar <mingo@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@fb.com, pjt@google.com,
luto@amacapital.net, Mike Galbraith <efault@gmx.de>,
torvalds@linux-foundation.org, Roman Gushchin <guro@fb.com>,
Juri Lelli <juri.lelli@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [PATCH] cpuset: Enforce that a child's cpus must be a subset of the parent
Date: Wed, 6 Jun 2018 13:56:35 -0700 [thread overview]
Message-ID: <20180606205635.GP1351649@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180531163826.GO12180@hirez.programming.kicks-ass.net>
Hello, Peter.
Sorry about late reply.
On Thu, May 31, 2018 at 06:38:26PM +0200, Peter Zijlstra wrote:
> > Yeah, for cpuset, it's messier, but it isn't different from hotunplug
> > scenario, right? I think the best we can do there is putting ancestor
> > operation on an equal footing as hotplug ops.
>
> Right, but hotplug is exceedingly rare, while I get the impression you
> think it is perfectly fine to recind on your resource grants.
Well, yeah, for a trivial example, imagine dynamic workload management
where you wanna restrict what a side-loaded batch workload can do on
and off peak hours. All other controllers can do that. It'd be a
really odd design trade-off if we make that really clumsy for cpuset
especially given that we wouldn't be gaining any actual
functionalities.
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <longman@redhat.com>, Zefan Li <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ingo Molnar <mingo@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@fb.com, pjt@google.com,
luto@amacapital.net, Mike Galbraith <efault@gmx.de>,
torvalds@linux-foundation.org, Roman Gushchin <guro@fb.com>,
Juri Lelli <juri.lelli@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [PATCH] cpuset: Enforce that a child's cpus must be a subset of the parent
Date: Wed, 6 Jun 2018 13:56:35 -0700 [thread overview]
Message-ID: <20180606205635.GP1351649@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180531163826.GO12180@hirez.programming.kicks-ass.net>
Hello, Peter.
Sorry about late reply.
On Thu, May 31, 2018 at 06:38:26PM +0200, Peter Zijlstra wrote:
> > Yeah, for cpuset, it's messier, but it isn't different from hotunplug
> > scenario, right? I think the best we can do there is putting ancestor
> > operation on an equal footing as hotplug ops.
>
> Right, but hotplug is exceedingly rare, while I get the impression you
> think it is perfectly fine to recind on your resource grants.
Well, yeah, for a trivial example, imagine dynamic workload management
where you wanna restrict what a side-loaded batch workload can do on
and off peak hours. All other controllers can do that. It'd be a
really odd design trade-off if we make that really clumsy for cpuset
especially given that we wouldn't be gaining any actual
functionalities.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-06 20:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 13:46 [PATCH] cpuset: Enforce that a child's cpus must be a subset of the parent Waiman Long
2018-05-30 13:46 ` Waiman Long
2018-05-30 14:00 ` Juri Lelli
2018-05-30 14:00 ` Juri Lelli
2018-05-31 1:25 ` Zefan Li
2018-05-31 1:25 ` Zefan Li
2018-05-31 1:25 ` Zefan Li
2018-05-31 7:43 ` Peter Zijlstra
2018-05-31 7:43 ` Peter Zijlstra
2018-05-31 8:12 ` Zefan Li
2018-05-31 8:12 ` Zefan Li
2018-05-31 8:12 ` Zefan Li
2018-05-31 8:26 ` Peter Zijlstra
2018-05-31 8:26 ` Peter Zijlstra
2018-05-31 8:41 ` Juri Lelli
2018-05-31 8:41 ` Juri Lelli
2018-05-31 8:42 ` Zefan Li
2018-05-31 8:42 ` Zefan Li
2018-05-31 8:42 ` Zefan Li
2018-05-31 13:22 ` Waiman Long
2018-05-31 13:22 ` Waiman Long
2018-05-31 15:58 ` Tejun Heo
2018-05-31 15:58 ` Tejun Heo
2018-05-31 16:16 ` Peter Zijlstra
2018-05-31 16:16 ` Peter Zijlstra
2018-05-31 16:19 ` Tejun Heo
2018-05-31 16:19 ` Tejun Heo
2018-05-31 16:38 ` Peter Zijlstra
2018-05-31 16:38 ` Peter Zijlstra
2018-06-06 20:56 ` Tejun Heo [this message]
2018-06-06 20:56 ` Tejun Heo
2018-05-31 16:28 ` Waiman Long
2018-05-31 16:28 ` Waiman Long
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=20180606205635.GP1351649@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=efault@gmx.de \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.