Hello, On Mon, Nov 06, 2017 at 05:26:38PM +0100, Paolo Valente wrote: > Yes. DEBUG_BLK_CGROUP will just serve to keep the for-debugging > subset switched off even when the dynamic parameter is on. > > We'll wait for possible counter-arguments from Tejun, and then start > to work on what you propose.
So, I think the only *really* required ones are io_serviced and the corresponding byte counts, which are tracked by blk-cgroup core anyway. Everything else can be hidden behind an obviously debug boot param, say, bfq.__DEBUG__extra_stats or whatever. Thanks. -- tejun
