Peter Zijlstra wrote:
On Sat, 2007-10-27 at 23:30 +0200, Peter Zijlstra wrote:
So in short, stick a struct backing_dev_info into whatever represents a
client, initialize it using bdi_init(), destroy using bdi_destroy().
Oh, and the most important point, make your fresh I_NEW inodes point to
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
On Sat, Oct 27, 2007 at 11:34:26AM +0200, Peter Zijlstra wrote:
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
On 10/27/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
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
On Sat, 2007-10-27 at 16:02 -0500, Steve French wrote:
On 10/27/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
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
On Sat, 2007-10-27 at 23:30 +0200, Peter Zijlstra wrote:
On Sat, 2007-10-27 at 16:02 -0500, Steve French wrote:
On 10/27/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
Hi,
I had me a little look at bdi usage in networked filesystems.
NFS, CIFS, (smbfs), AFS, CODA and NCP
And
