linux-kernel - Re: [PATCH block/for-next 4/4] block: implement bio_associate

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] [day] [month] [year] [list]

Message-ID: <20150106231253.GC24106@htj.dyndns.org>
Date:	Tue, 6 Jan 2015 18:12:53 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH block/for-next 4/4] block: implement bio_associate_blkcg()

Hello, Vivek.

Sorry about the delay.

On Thu, Nov 20, 2014 at 04:15:06PM -0500, Vivek Goyal wrote:
> Not sure what can be done about this. May be a notion of per
> block cgroup per device io context and always use that io context
> when bio has cgroup info but not io context info. 

I think the right thing to do here is having a dedicated ioc for
writeback traffic per cgroup and channel writebacks of the cgroup
through there.  We'd be simply extending the current global model into
each group.

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/