From: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
To: Vivek Goyal <vgoyal@redhat.com>, Jens Axboe <jens.axboe@oracle.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Divyesh Shah <dpshah@google.com>,
Nauman Rafique <nauman@google.com>
Subject: Re: [PATCH] blk-cgroup: config options re-arrangement
Date: Fri, 23 Apr 2010 15:44:46 +0800 [thread overview]
Message-ID: <4BD14FEE.1090407@cn.fujitsu.com> (raw)
In-Reply-To: <20100422223705.GI3228@redhat.com>
Vivek Goyal wrote:
> This patch fixes few usability and configurability issues.
>
> o All the cgroup based controller options are configurable from
> "Genral Setup/Control Group Support/" menu. blkio is the only exception.
> Hence make this option visible in above menu and make it configurable from
> there to bring it inline with rest of the cgroup based controllers.
>
> o Get rid of CONFIG_DEBUG_CFQ_IOSCHED.
>
> This option currently does two things.
>
> - Enable printing of cgroup paths in blktrace
> - Enables CONFIG_DEBUG_BLK_CGROUP, which in turn displays additional stat
> files in cgroup.
>
> If we are using group scheduling, blktrace data is of not really much use
> if cgroup information is not present. To get this data, currently one has to
> also enable CONFIG_DEBUG_CFQ_IOSCHED, which in turn brings the overhead of
> all the additional debug stat files which is not desired.
>
> Hence, this patch moves printing of cgroup paths under
> CONFIG_CFQ_GROUP_IOSCHED.
>
> This allows us to get rid of CONFIG_DEBUG_CFQ_IOSCHED completely. Now all
> the debug stat files are controlled only by CONFIG_DEBUG_BLK_CGROUP which
> can be enabled through config menu.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
This patch looks good to me.
Reviewed-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
next prev parent reply other threads:[~2010-04-23 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 22:37 [PATCH] blk-cgroup: config options re-arrangement Vivek Goyal
2010-04-22 23:42 ` Divyesh Shah
2010-04-23 7:44 ` Gui Jianfeng [this message]
2010-04-26 17:18 ` Vivek Goyal
2010-04-26 17:27 ` Jens Axboe
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=4BD14FEE.1090407@cn.fujitsu.com \
--to=guijianfeng@cn.fujitsu.com \
--cc=dpshah@google.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nauman@google.com \
--cc=vgoyal@redhat.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