From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Li Zefan" <lizefan@huawei.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, "Mike Galbraith" <efault@gmx.de>,
"Christian Brauner" <christian.brauner@canonical.com>,
"Stéphane Graber" <stgraber@ubuntu.com>,
"Serge Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH v3] cpuset: Enable cpuset controller in default hierarchy
Date: Thu, 26 Oct 2017 07:39:08 -0700 [thread overview]
Message-ID: <20171026143908.GD59538@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <db119820-84d4-7ccb-e65a-966d2d7aaf02@redhat.com>
Hello, Waiman.
On Wed, Oct 25, 2017 at 11:50:34AM -0400, Waiman Long wrote:
> Ping! Any comment on this patch?
Sorry about the lack of response. Here are my two thoughts.
1. I'm not really sure about the memory part. Mostly because of the
way it's configured and enforced is completely out of step with how
mm behaves in general. I'd like to get more input from mm folks on
this.
2. I want to think more about how we expose the effective settings.
Not that anything is wrong with what cpuset does, but more that I
wanna ensure that it's something we can follow in other cases where
we have similar hierarchical property propagation.
We're likely too late for the coming merge window. Let's handle it
during the next window.
Thanks and my apologies for the delay.
--
tejun
next prev parent reply other threads:[~2017-10-26 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 21:10 [PATCH v3] cpuset: Enable cpuset controller in default hierarchy Waiman Long
2017-10-25 15:50 ` Waiman Long
2017-10-26 14:39 ` Tejun Heo [this message]
[not found] ` <20171026143908.GD59538-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2017-10-26 18:12 ` Waiman Long
[not found] ` <2814be69-8dc1-b2f8-406e-cc4dda289d94-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-26 20:59 ` Christian Brauner
2017-11-14 17:49 ` Waiman Long
[not found] ` <1507324230-22996-1-git-send-email-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-27 21:04 ` Tejun Heo
2017-11-27 21:19 ` Waiman Long
[not found] ` <8a5ba419-2b02-5b6a-462f-34106cc575ab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-27 21:42 ` Tejun Heo
2017-11-27 21:47 ` 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=20171026143908.GD59538@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=christian.brauner@canonical.com \
--cc=corbet@lwn.net \
--cc=efault@gmx.de \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=serge@hallyn.com \
--cc=stgraber@ubuntu.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