From: Vivek Goyal <vgoyal@redhat.com>
To: Chad Talbott <ctalbott@google.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Nauman Rafique <nauman@google.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [RFC] blk-cgroup: Allow creation of hierarchical cgroups
Date: Wed, 3 Nov 2010 09:26:07 -0400 [thread overview]
Message-ID: <20101103132607.GA2920@redhat.com> (raw)
In-Reply-To: <AANLkTi=U4MY1jEE60arAPz0iKbVcV__3WfHjU3eikaeh@mail.gmail.com>
On Tue, Nov 02, 2010 at 05:11:24PM -0700, Chad Talbott wrote:
> On Tue, Nov 2, 2010 at 3:20 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> > o Allow hierarchical cgroup creation for blkio controller
>
> Vivek,
>
> This patch looks fine, and we use similar code. I'd be even more
> interested in directing effort at Gui's patchset that fully implements
> hierarchy. If there are specific details that are blocking adoption
> of that code, let's address them.
Hi Chad,
My primary concern was re-organizing the code in such a way so that we
treat queues and groups at the same level. I think Gui is now addressing
those concerns.
I have detailed my concerns in this thread. (You are CCed though in the
thread).
http://lkml.org/lkml/2010/8/30/30
Thanks
Vivek
next prev parent reply other threads:[~2010-11-03 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 22:20 [RFC] blk-cgroup: Allow creation of hierarchical cgroups Vivek Goyal
2010-11-03 0:11 ` Chad Talbott
2010-11-03 13:26 ` Vivek Goyal [this message]
2010-11-03 2:27 ` Balbir Singh
2010-11-03 4:14 ` Gui Jianfeng
2010-11-03 15:03 ` Ciju Rajan K
2010-11-15 15:28 ` Vivek Goyal
2010-11-15 18:38 ` Jens Axboe
2010-11-16 2:50 ` KAMEZAWA Hiroyuki
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=20101103132607.GA2920@redhat.com \
--to=vgoyal@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=ctalbott@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jaxboe@fusionio.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=nauman@google.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;
as well as URLs for NNTP newsgroup(s).