From: Peter Zijlstra <peterz@infradead.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, Paul Turner <pjt@google.com>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] sched/fair: make CFS bandwidth slice per cpu group
Date: Mon, 30 Apr 2018 21:42:51 +0200 [thread overview]
Message-ID: <20180430194251.GB12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180430192925.12589-1-xiyou.wangcong@gmail.com>
On Mon, Apr 30, 2018 at 12:29:25PM -0700, Cong Wang wrote:
> Currently, the sched_cfs_bandwidth_slice_us is a global setting which
> affects all cgroups. Different groups may want different values based
> on their own workload, one size doesn't fit all. The global pool filled
> periodically is per cgroup too, they should have the right to distribute
> their own quota to each local CPU with their own frequency.
Why.. what happens? This doesn't really tell us anything.
next prev parent reply other threads:[~2018-04-30 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 19:29 Cong Wang
2018-04-30 19:42 ` Peter Zijlstra [this message]
2018-04-30 20:37 ` Cong Wang
2018-05-01 7:11 ` Peter Zijlstra
2018-05-01 18:06 ` Cong Wang
2018-05-01 0:29 ` kbuild test robot
2018-05-01 0:29 ` [RFC PATCH] sched/fair: tg_set_cfs_slice() can be static kbuild test robot
2018-05-01 0:31 ` [PATCH] sched/fair: make CFS bandwidth slice per cpu group kbuild test robot
2018-05-01 0:57 ` kbuild test robot
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=20180430194251.GB12217@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=xiyou.wangcong@gmail.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®