Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756074AbXJBL2S (ORCPT ); Tue, 2 Oct 2007 07:28:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752677AbXJBL2J (ORCPT ); Tue, 2 Oct 2007 07:28:09 -0400 Received: from smtp.ustc.edu.cn ([202.38.64.16]:58199 "HELO ustc.edu.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S1752646AbXJBL2G (ORCPT ); Tue, 2 Oct 2007 07:28:06 -0400 Message-ID: <391324486.02635@ustc.edu.cn> X-EYOUMAIL-SMTPAUTH: wfg@mail.ustc.edu.cn Date: Tue, 2 Oct 2007 19:28:02 +0800 From: Fengguang Wu To: Kay Sievers Cc: Peter Zijlstra , Andrew Morton , linux-kernel@vger.kernel.org, Jens Axboe , Fengguang Wu , greg@kroah.com Subject: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24) Message-ID: <20071002112802.GA12607@mail.ustc.edu.cn> References: <20071001142222.fcaa8d57.akpm@linux-foundation.org> <1191313025.13204.30.camel@twins> <20071002013148.18958af2.akpm@linux-foundation.org> <1191314911.13204.41.camel@twins> <3ae72650710020331o2ce5bd20wccc1964855279796@mail.gmail.com> <1191321861.13204.53.camel@twins> <391322057.11200@ustc.edu.cn> <3ae72650710020422r5d873289j3d1565dfa21e1ede@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ae72650710020422r5d873289j3d1565dfa21e1ede@mail.gmail.com> X-GPG-Fingerprint: 53D2 DDCE AB5C 8DC6 188B 1CB1 F766 DA34 8D8B 1C6D User-Agent: Mutt/1.5.16 (2007-06-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1122 Lines: 25 On Tue, Oct 02, 2007 at 01:22:32PM +0200, Kay Sievers wrote: > On 10/2/07, Fengguang Wu 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. Yes, but they have no /queue/ subdir, which (for sda etc.) exports both elevator and bdi variables. Now we want to access these bdi variables... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/