linux-kernel - Re: [PATCH 01/17] blkcg: make CONFIG_BLK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jan 2012 07:34:54 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	axboe@...nel.dk, ctalbott@...gle.com, rni@...gle.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/17] blkcg: make CONFIG_BLK_CGROUP bool

Hello,

On Mon, Jan 23, 2012 at 10:00:51AM -0500, Vivek Goyal wrote:
> On Sat, Jan 21, 2012 at 07:25:09PM -0800, Tejun Heo wrote:
> > Block cgroup core can be built as module; however, it isn't too useful
> > as blk-throttle can only be built-in and cfq-iosched is usually the
> > default built-in scheduler.  Scheduled blkcg cleanup requires calling
> > into blkcg from block core.  To simplify that, disallow building blkcg
> > as module by making CONFIG_BLK_CGROUP bool.
> > 
> > If building blkcg core as module really matters, which I doubt, we can
> > revisit it after blkcg API cleanup.
> 
> I think not allowing compiling blk-cgroup as module is a good thing.

Sure, it's nice.  It just is mostly pointless at this point and
hinders API cleanup.  As written above, if this really matters, let's
add it back after cleanup is complete.

> >  config IOSCHED_CFQ
> >  	tristate "CFQ I/O scheduler"
> > -	# If BLK_CGROUP is a module, CFQ has to be built as module.
> > -	depends on (BLK_CGROUP=m && m) || !BLK_CGROUP || BLK_CGROUP=y
> > +	depends on BLK_CGROUP
> 
> You don't need above dependency now. Otherwise if BLK_CGROUP=n then one
> can't use CFQ. We just want cfq group scheduling to be dependent on
> BLK_CGROUP.

Ooh, right, will drop the line.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/