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

Message-ID: <3ae72650710020422r5d873289j3d1565dfa21e1ede@mail.gmail.com>
Date:	Tue, 2 Oct 2007 13:22:32 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Fengguang Wu" <wfg@...l.ustc.edu.cn>
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 10/2/07, Fengguang Wu <wfg@...l.ustc.edu.cn> wrote:
> On Tue, Oct 02, 2007 at 12:44:21PM +0200, Peter Zijlstra wrote:
> > On Tue, 2007-10-02 at 12:31 +0200, Kay Sievers wrote:
> >
> > > What would be the point in another top-level tree for device
> > > information? All devices you are exporting information for, are
> > > already in the sysfs tree, right?
> >
> > Never did find NFS mounts/servers/superblocks or whatever constitutes a
> > BDI for NFS in there. Same goes for all other networked filesystems for
> > that matter.
>
> And loop/md/dm devices...

Hmm, /sys/block/mdX, /sys/block/loopX, /sys/block/dm-X are all there today.

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/