linux-kernel - Re: [PATCH RFC] fsio: filesystem io accounting cgroup

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: <20130709125734.GA2478@htj.dyndns.org>
Date:	Tue, 9 Jul 2013 05:57:34 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
Cc:	Vivek Goyal <vgoyal@...hat.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.cz>,
	cgroups@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
	Sha Zhengju <handai.szj@...il.com>, devel@...nvz.org,
	Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH RFC] fsio: filesystem io accounting cgroup

Hello,

On Tue, Jul 09, 2013 at 12:28:15PM +0400, Konstantin Khlebnikov wrote:
> Yep, blkio has plenty problems and flaws and I don't get how it's related
> to vfs layer, dirty set control and non-disk or network backed filesystems.
> Any problem can be fixed by introducing new abstract layer, except too many
> abstraction levels. Cgroup is pluggable subsystem, blkio has it's own plugins
> and it's build on top of io scheduler plugin. All this stuff always have worked

What does that have to do with anything?

> with block devices. Now you suggest to handle all filesystems in this stack.
> I think binding them to unrealated cgroup is rough leveling violation.

How is blkio unrelated to filesystems mounted on block devices?
You're suggesting a duplicate solution which can't be complete.

> NFS cannot be controlled only by network throttlers because we
> cannot slow down writeback process when it happens, we must slow
> down tasks who generates dirty memory.

That's exactly the same problem why blkio doesn't work for async IOs
right now, so if you're interested in the area, please contribute to
fixing that problem.

> Plus it's close to impossible to separate several workloads if they
> share one NFS sb.

Again, the same problem with blkio.  We need separate pressure
channels on bdi for each cgroup.

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/