From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Tejun Heo <tj@kernel.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
mingo@redhat.com, lizefan@huawei.com, pjt@google.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-api@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource group and PRIO_RGRP
Date: Fri, 08 Apr 2016 05:13:56 +0200 [thread overview]
Message-ID: <1460085236.4026.15.camel@gmail.com> (raw)
In-Reply-To: <20160407202344.GA22509@cmpxchg.org>
On Thu, 2016-04-07 at 16:23 -0400, Johannes Weiner wrote:
> Mike, is that the one you referred to with one group per customer
> account? If so, would you have a pointer to where you outline it?
The usage I loosely outlined, I did in this thread. All of the gory
details I do not have, do not want, and could not provide if I did.
-Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Galbraith <umgwanakikbuti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
pjt-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-team-b10kYP2dOMg@public.gmane.org
Subject: Re: [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource group and PRIO_RGRP
Date: Fri, 08 Apr 2016 05:13:56 +0200 [thread overview]
Message-ID: <1460085236.4026.15.camel@gmail.com> (raw)
In-Reply-To: <20160407202344.GA22509-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
On Thu, 2016-04-07 at 16:23 -0400, Johannes Weiner wrote:
> Mike, is that the one you referred to with one group per customer
> account? If so, would you have a pointer to where you outline it?
The usage I loosely outlined, I did in this thread. All of the gory
details I do not have, do not want, and could not provide if I did.
-Mike
next prev parent reply other threads:[~2016-04-08 3:14 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 15:41 [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource group and PRIO_RGRP Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 01/10] cgroup: introduce cgroup_[un]lock() Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 02/10] cgroup: un-inline cgroup_path() and friends Tejun Heo
2016-03-11 15:41 ` [PATCH 03/10] cgroup: introduce CGRP_MIGRATE_* flags Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 04/10] signal: make put_signal_struct() public Tejun Heo
2016-03-11 15:41 ` [PATCH 05/10] cgroup, fork: add @new_rgrp_cset[p] and @clone_flags to cgroup fork callbacks Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 06/10] cgroup, fork: add @child and @clone_flags to threadgroup_change_begin/end() Tejun Heo
2016-03-11 15:41 ` [PATCH 07/10] cgroup: introduce resource group Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 08/10] cgroup: implement rgroup control mask handling Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 15:41 ` [PATCH 09/10] cgroup: implement rgroup subtree migration Tejun Heo
2016-03-11 15:41 ` [PATCH 10/10] cgroup, sched: implement PRIO_RGRP for {set|get}priority() Tejun Heo
2016-03-11 15:41 ` Tejun Heo
2016-03-11 16:05 ` Example program for PRIO_RGRP Tejun Heo
2016-03-11 16:05 ` Tejun Heo
2016-03-12 6:26 ` [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource group and PRIO_RGRP Mike Galbraith
2016-03-12 6:26 ` Mike Galbraith
2016-03-12 17:04 ` Mike Galbraith
2016-03-12 17:04 ` Mike Galbraith
2016-03-12 17:13 ` cgroup NAKs ignored? " Ingo Molnar
2016-03-12 17:13 ` Ingo Molnar
2016-03-13 14:42 ` Tejun Heo
2016-03-13 14:42 ` Tejun Heo
2016-03-13 15:00 ` Tejun Heo
2016-03-13 15:00 ` Tejun Heo
2016-03-13 17:40 ` Mike Galbraith
2016-03-13 17:40 ` Mike Galbraith
2016-04-07 0:00 ` Tejun Heo
2016-04-07 0:00 ` Tejun Heo
2016-04-07 3:26 ` Mike Galbraith
2016-04-07 3:26 ` Mike Galbraith
2016-03-14 2:23 ` Mike Galbraith
2016-03-14 2:23 ` Mike Galbraith
2016-03-14 11:30 ` Peter Zijlstra
2016-03-14 11:30 ` Peter Zijlstra
2016-04-06 15:58 ` Tejun Heo
2016-04-06 15:58 ` Tejun Heo
2016-04-06 15:58 ` Tejun Heo
2016-04-07 6:45 ` Peter Zijlstra
2016-04-07 6:45 ` Peter Zijlstra
2016-04-07 7:35 ` Johannes Weiner
2016-04-07 7:35 ` Johannes Weiner
2016-04-07 8:05 ` Mike Galbraith
2016-04-07 8:05 ` Mike Galbraith
2016-04-07 8:08 ` Peter Zijlstra
2016-04-07 8:08 ` Peter Zijlstra
2016-04-07 9:28 ` Johannes Weiner
2016-04-07 9:28 ` Johannes Weiner
2016-04-07 10:42 ` Peter Zijlstra
2016-04-07 10:42 ` Peter Zijlstra
2016-04-07 19:45 ` Tejun Heo
2016-04-07 19:45 ` Tejun Heo
2016-04-07 20:25 ` Peter Zijlstra
2016-04-07 20:25 ` Peter Zijlstra
2016-04-08 20:11 ` Tejun Heo
2016-04-08 20:11 ` Tejun Heo
2016-04-09 6:16 ` Mike Galbraith
2016-04-09 6:16 ` Mike Galbraith
2016-04-09 13:39 ` Peter Zijlstra
2016-04-09 13:39 ` Peter Zijlstra
2016-04-12 22:29 ` Tejun Heo
2016-04-12 22:29 ` Tejun Heo
2016-04-13 7:43 ` Mike Galbraith
2016-04-13 7:43 ` Mike Galbraith
2016-04-13 15:59 ` Tejun Heo
2016-04-13 19:15 ` Mike Galbraith
2016-04-13 19:15 ` Mike Galbraith
2016-04-14 6:07 ` Mike Galbraith
2016-04-14 19:57 ` Tejun Heo
2016-04-14 19:57 ` Tejun Heo
2016-04-15 2:42 ` Mike Galbraith
2016-04-15 2:42 ` Mike Galbraith
2016-04-09 16:02 ` Peter Zijlstra
2016-04-09 16:02 ` Peter Zijlstra
2016-04-07 8:28 ` Peter Zijlstra
2016-04-07 8:28 ` Peter Zijlstra
2016-04-07 19:04 ` Johannes Weiner
2016-04-07 19:04 ` Johannes Weiner
2016-04-07 19:31 ` Peter Zijlstra
2016-04-07 19:31 ` Peter Zijlstra
2016-04-07 20:23 ` Johannes Weiner
2016-04-07 20:23 ` Johannes Weiner
2016-04-08 3:13 ` Mike Galbraith [this message]
2016-04-08 3:13 ` Mike Galbraith
2016-03-15 17:21 ` Michal Hocko
2016-03-15 17:21 ` Michal Hocko
2016-04-06 21:53 ` Tejun Heo
2016-04-06 21:53 ` Tejun Heo
2016-04-07 6:40 ` Peter Zijlstra
2016-04-07 6:40 ` Peter Zijlstra
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=1460085236.4026.15.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tj@kernel.org \
--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.