From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steve French <smfrench@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
sfrench@samba.org, jaharkes@cs.cmu.edu,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Networked filesystems vs backing_dev_info
Date: Sun, 28 Oct 2007 00:46:07 -0700 [thread overview]
Message-ID: <47243E3F.9060307@vc.cvut.cz> (raw)
In-Reply-To: <1193521041.27652.37.camel@twins>
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
> this bdi struct.
>
>> Mark it congested once you have 50 (or more) outstanding requests, clear
>> congestion when you drop below 50.
>> and you should be set.
Thanks. Unfortunately I do not think that NCPFS will switch to
backing_dev_info - it uses pagecache only for symlinks and directories,
and even if it would use pagecache, as most of servers refuse concurrent
requests even if TCP is used as a transport, there can be only one
request in flight...
Petr
P.S.: And if anyone wants to step in as ncpfs maintainer, feel free. I
did not see NetWare server for over year now...
prev parent reply other threads:[~2007-10-28 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 9:34 Networked filesystems vs backing_dev_info Peter Zijlstra
2007-10-27 15:22 ` Jan Harkes
2007-10-27 15:32 ` Peter Zijlstra
2007-10-27 21:02 ` Steve French
2007-10-27 21:30 ` Peter Zijlstra
2007-10-27 21:37 ` Peter Zijlstra
2007-10-28 7:46 ` Petr Vandrovec [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47243E3F.9060307@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox