public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	Gui Jianfeng <GuiJianfeng@cn.fujitsu.com>,
	Ben Blum <bblum@andrew.cmu.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	"containers@lists.osdl.org" <containers@lists.osdl.org>
Subject: [PATCH] block: make CONFIG_BLK_CGROUP visible
Date: Mon, 15 Mar 2010 11:18:13 +0800	[thread overview]
Message-ID: <4B9DA6F5.3070606@cn.fujitsu.com> (raw)

Make the config visible, so we can choose from CONFIG_BLK_CGROUP=y
and CONFIG_BLK_CGROUP=m when CONFIG_IOSCHED_CFQ=m.

Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
 block/Kconfig |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/block/Kconfig b/block/Kconfig
index 62a5921..906950c 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -78,8 +78,9 @@ config BLK_DEV_INTEGRITY
 	Protection.  If in doubt, say N.
 
 config BLK_CGROUP
-	tristate
+	tristate "Block cgroup support"
 	depends on CGROUPS
+	depends on CFQ_GROUP_IOSCHED
 	default n
 	---help---
 	Generic block IO controller cgroup interface. This is the common
@@ -91,7 +92,7 @@ config BLK_CGROUP
 	to such task groups.
 
 config DEBUG_BLK_CGROUP
-	bool
+	bool "Block cgroup debugging help"
 	depends on BLK_CGROUP
 	default n
 	---help---
-- 
1.6.3


             reply	other threads:[~2010-03-15  3:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  3:18 Li Zefan [this message]
2010-03-15  4:31 ` [PATCH] block: make CONFIG_BLK_CGROUP visible Ben Blum
2010-03-15 11:57 ` Jens Axboe
2010-03-16  1:42   ` Li Zefan
2010-03-16  7:56     ` Jens Axboe
2010-03-15 13:21 ` Vivek Goyal
2010-03-16  1:36   ` Li Zefan
2010-03-16 13:53     ` Vivek Goyal

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=4B9DA6F5.3070606@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=GuiJianfeng@cn.fujitsu.com \
    --cc=bblum@andrew.cmu.edu \
    --cc=containers@lists.osdl.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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