From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Networked filesystems vs backing_dev_info Date: Sat, 27 Oct 2007 11:34:26 +0200 Message-ID: <1193477666.5648.61.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: David Howells , sfrench@samba.org, jaharkes@cs.cmu.edu, Andrew Morton , vandrove@vc.cvut.cz To: linux-kernel , linux-fsdevel Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:47159 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751607AbXJ0JfD (ORCPT ); Sat, 27 Oct 2007 05:35:03 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, I had me a little look at bdi usage in networked filesystems. NFS, CIFS, (smbfs), AFS, CODA and NCP And of those, NFS is the only one that I could find that creates backing_dev_info structures. The rest seems to fall back to default_backing_dev_info. With my recent per bdi dirty limit patches the bdi has become more important than it has been in the past. While falling back to the default_backing_dev_info isn't wrong per-se, it isn't right either. Could I implore the various maintainers to look into this issue for their respective filesystem. I'll try and come up with some patches to address this, but feel free to beat me to it. peterz