[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180319162654.GR2943022@devbig577.frc2.facebook.com>
Date: Mon, 19 Mar 2018 09:26:54 -0700
From: Tejun Heo <tj@...nel.org>
To: Waiman Long <longman@...hat.com>
Cc: Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
kernel-team@...com, pjt@...gle.com, luto@...capital.net,
efault@....de, torvalds@...ux-foundation.org,
Roman Gushchin <guro@...com>
Subject: Re: [PATCH v5 2/2] cpuset: Add cpuset.flags control knob to v2
Hello, Waiman.
On Thu, Mar 15, 2018 at 05:20:42PM -0400, Waiman Long wrote:
> + The currently supported flag is:
> +
> + sched_load_balance
> + When it is not set, there will be no load balancing
> + among CPUs on this cpuset. Tasks will stay in the
> + CPUs they are running on and will not be moved to
> + other CPUs.
> +
> + When it is set, tasks within this cpuset will be
> + load-balanced by the kernel scheduler. Tasks will be
> + moved from CPUs with high load to other CPUs within
> + the same cpuset with less load periodically.
Hmm... looks like this is something which can be decided by the cgroup
itself and should be made delegatable. Given that different flags
might need different delegation settings and the precedence of
memory.oom_group, I think it'd be better to make the flags separate
bool files - ie. cpuset.sched_load_balance which contains 0/1 and
marked delegatable.
Thanks.
--
tejun
Powered by blists - more mailing lists