linux-kernel - Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)

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:	Wed, 03 Oct 2007 12:15:06 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
	Fengguang Wu <fengguang.wu@...il.com>, greg@...ah.com
Subject: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)

On Tue, 2007-10-02 at 22:05 +1000, Nick Piggin wrote:
> On Tuesday 02 October 2007 21:40, Peter Zijlstra wrote:
> > On Tue, 2007-10-02 at 13:21 +0200, Kay Sievers wrote:
> 
> > > How about adding this information to the tree then, instead of
> > > creating a new top-level hack, just because something that you think
> > > you need doesn't exist.
> >
> > So you suggest adding all the various network filesystems in there
> > (where?), and adding the concept of a BDI, and ensuring all are properly
> > linked together - somehow. Feel free to do so.
> 
> Would something fit better under /sys/fs/? At least filesystems are
> already an existing concept to userspace.

Sounds at least less messy than an new top-level directory.

But again, if it's "device" releated, like the name suggests, it should
be reachable from the device tree.
Which userspace tool is supposed to set these values, and at what time?
An init-script, something at device discovery/setup? If that is is ever
going to be used in a hotplug setup, you really don't want to go look
for directories with magic device names in another disconnected tree.

Kay

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