linux-kernel - Re: [PATCH 08/17] blkcg: shoot down blkio

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]

Message-ID: <20120123162840.GJ25986@redhat.com>
Date:	Mon, 23 Jan 2012 11:28:40 -0500
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	axboe@...nel.dk, ctalbott@...gle.com, rni@...gle.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/17] blkcg: shoot down blkio_groups on elevator switch

On Mon, Jan 23, 2012 at 08:20:35AM -0800, Tejun Heo wrote:
> On Mon, Jan 23, 2012 at 11:13:08AM -0500, Vivek Goyal wrote:
> > How about draining throttle groups only on queue exit (blk_cleanup_queue())
> > and not on elevator switch.
> 
> It's for possible policy changes and to fully manage blkg from blkcg.
> blkg itself needs to change as applied policies change and need to be
> flushed.

Can we avoid integrating everything into single blkg. What's wrong with
separate blkg for separage policy. In this case we just don't have the
flexbility to change throttling policy. If it is compiled in, it gets
activated. The only configurable thing is IO scheduler and these groups
will be cleaned up.

So keeping blkg separate for separate policy gives us this flexibility
that we don't have to cleanup throttling data and keep the throttling
rules persistent across elevator switch.

Thanks
Vivek
--
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/