From: Vivek Goyal <vgoyal@redhat.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: Nauman Rafique <nauman@google.com>, Jens Axboe <axboe@kernel.dk>,
Jeff Moyer <jmoyer@redhat.com>, Divyesh Shah <dpshah@google.com>,
Corrado Zoccolo <czoccolo@gmail.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC] [PATCH] cfq-iosched: add cfq group hierarchical scheduling support
Date: Wed, 1 Sep 2010 22:20:08 -0400 [thread overview]
Message-ID: <20100902022008.GA7901@redhat.com> (raw)
In-Reply-To: <4C7E13CE.7070603@cn.fujitsu.com>
On Wed, Sep 01, 2010 at 04:50:22PM +0800, Gui Jianfeng wrote:
[..]
> Hi Vivek,
>
> Even if we mount cpu and blkio together, to me, it's ok for cpu and blkio
> having their own logic, since they are totally different cgroup subsystems.
>
> >
> > - To me, both group and cfq queue are children of root group and it
> > makes sense to treat them independent childrens instead of putting
> > all the queues in one logical group which inherits the weight of
> > parent.
> >
> > - With this new scheme, I am finding it hard to visualize the hierachy.
> > How do you assign the weights to queue entities of a group. It is more
> > like a invisible group with-in group. We shall have to create new
> > tunable which can speicy the weight for this hidden group.
>
> For the time being, the root "qse" weight is 1000 and others is 500, they don't
> inherit the weight of parent. I was thinking that maybe we can determine the qse
> weight in term of the queue number and weight in this group and subgroups.
If you decide queue weight in terms of queue number, then you are back to
the same problem Nauman was mentioning that share of a group is not fixed
and depends on number of queues in the group.
Vivek
next prev parent reply other threads:[~2010-09-02 2:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 6:50 [RFC] [PATCH] cfq-iosched: add cfq group hierarchical scheduling support Gui Jianfeng
2010-08-30 18:20 ` Chad Talbott
2010-08-31 0:35 ` Gui Jianfeng
2010-08-30 20:36 ` Vivek Goyal
2010-08-31 0:29 ` Gui Jianfeng
2010-08-31 12:57 ` Vivek Goyal
2010-08-31 15:40 ` Nauman Rafique
2010-08-31 19:25 ` Vivek Goyal
2010-09-01 8:50 ` Gui Jianfeng
2010-09-01 15:49 ` Nauman Rafique
2010-09-01 17:10 ` Vivek Goyal
2010-09-01 17:15 ` Nauman Rafique
2010-09-01 17:21 ` Vivek Goyal
2010-09-02 0:30 ` Gui Jianfeng
2010-09-02 2:20 ` Vivek Goyal [this message]
2010-09-01 8:48 ` Gui Jianfeng
2010-09-01 9:02 ` KAMEZAWA Hiroyuki
2010-09-02 2:29 ` Vivek Goyal
2010-09-02 2:42 ` 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=20100902022008.GA7901@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=czoccolo@gmail.com \
--cc=dpshah@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jmoyer@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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