From: Vivek Goyal <vgoyal@redhat.com>
To: Divyesh Shah <dpshah@google.com>
Cc: Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Jens Axboe <axboe@kernel.dk>, Shaohua Li <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Chad Talbott <ctalbott@google.com>
Subject: Re: [PATCH 5/6 v4] cfq-iosched: CFQ group hierarchical scheduling and use_hierarchy interface
Date: Wed, 16 Feb 2011 13:06:28 -0500 [thread overview]
Message-ID: <20110216180628.GF14653@redhat.com> (raw)
In-Reply-To: <AANLkTinUcSxJZ24NeUwQ_6W4=+atRWX-7G9K5iymuOsz@mail.gmail.com>
On Wed, Feb 16, 2011 at 09:28:07AM -0800, Divyesh Shah wrote:
> On Wed, Feb 16, 2011 at 9:22 AM, Divyesh Shah <dpshah@google.com> wrote:
> > On Tue, Feb 15, 2011 at 5:44 PM, Gui Jianfeng
> > <guijianfeng@cn.fujitsu.com> wrote:
> >> Hmm, it seems memcg aggregating stats in parent group.
> >> But do we really need to do that in kernel? I think it's easier to do it in
> >> userland, and it makes kernel much simpler.
> >>
> >
> > I would prefer having stats aggregated up the hierarchy. One trick we
> > used at Google earlier was to do lazy updates for most stats. So we
>
> Note that this was on ancient version of the blkio controller :). As
> Vivek mentioned,
> it may be ok to add the hierarchical accounting later.
One improvement we can probably do is make accounting per cpu and make
it lockless.
Thanks
Vivek
next prev parent reply other threads:[~2011-02-16 18:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D51ED26.8050809@cn.fujitsu.com>
2011-02-10 7:46 ` [PATCH 1/6 v4] cfq-iosched: Introduce cfq_entity for CFQ queue Gui Jianfeng
2011-02-10 7:47 ` [PATCH 2/6 v4] cfq-iosched: Introduce cfq_entity for CFQ group Gui Jianfeng
2011-02-10 7:47 ` [PATCH 3/6 v4] cfq-iosched: Introduce vdisktime and io weight for CFQ queue Gui Jianfeng
2011-02-10 19:29 ` Vivek Goyal
2011-02-12 1:20 ` Gui Jianfeng
2011-02-14 16:58 ` Vivek Goyal
2011-02-15 1:53 ` Gui Jianfeng
2011-02-15 14:24 ` Vivek Goyal
2011-02-16 1:06 ` Gui Jianfeng
2011-02-14 18:13 ` Vivek Goyal
2011-02-15 1:46 ` Gui Jianfeng
2011-02-18 6:04 ` Gui Jianfeng
2011-02-18 14:54 ` Vivek Goyal
2011-02-21 1:13 ` Gui Jianfeng
2011-02-21 5:55 ` Gui Jianfeng
2011-02-21 15:41 ` Vivek Goyal
2011-02-14 23:32 ` Justin TerAvest
2011-02-15 1:44 ` Gui Jianfeng
2011-02-15 14:21 ` Vivek Goyal
2011-02-10 7:47 ` [PATCH 4/6 v4] cfq-iosched: Extract some common code of service tree handling for CFQ queue and CFQ group Gui Jianfeng
2011-02-10 7:47 ` [PATCH 5/6 v4] cfq-iosched: CFQ group hierarchical scheduling and use_hierarchy interface Gui Jianfeng
2011-02-10 20:57 ` Vivek Goyal
2011-02-12 2:21 ` Gui Jianfeng
2011-02-14 18:04 ` Vivek Goyal
2011-02-15 2:38 ` Gui Jianfeng
2011-02-15 14:27 ` Vivek Goyal
2011-02-16 1:44 ` Gui Jianfeng
2011-02-16 14:17 ` Vivek Goyal
2011-02-17 1:22 ` Gui Jianfeng
2011-02-16 17:22 ` Divyesh Shah
2011-02-16 17:28 ` Divyesh Shah
2011-02-16 18:06 ` Vivek Goyal [this message]
2011-02-14 3:20 ` Gui Jianfeng
2011-02-14 18:10 ` Vivek Goyal
2011-02-17 0:31 ` Justin TerAvest
2011-02-17 1:21 ` Gui Jianfeng
2011-02-17 17:36 ` Justin TerAvest
2011-02-18 1:14 ` Gui Jianfeng
2011-02-17 10:39 ` Alan Cox
2011-02-10 7:47 ` [PATCH 6/6 v4] blkio-cgroup: Document for blkio.use_hierarchy interface Gui Jianfeng
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=20110216180628.GF14653@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=ctalbott@google.com \
--cc=dpshah@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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