From: Simon Kirby <sim@netnation.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client behavior on close
Date: Wed, 2 Jun 2004 08:41:46 -0700 [thread overview]
Message-ID: <20040602154146.GA2481@netnation.com> (raw)
In-Reply-To: <1086159327.10317.2.camel@lade.trondhjem.org>
Hi Trond,
On Tue, Jun 01, 2004 at 11:55:27PM -0700, Trond Myklebust wrote:
> P? m? , 31/05/2004 klokka 14:38, skreiv Simon Kirby:
>
> > Is the NFS client required to write all data on close?
>
> Yes. That is the basis of the NFSv2/v3 caching model...
In that case, is there any reason why we would ever want to wait
before sending data to the server, except for a minimal time to allow
merging into wsize blocks? With no delay, avoiding the write to disk
for temporary files can still happen on the server side (async).
Mass file writes from a single thread should be faster if the client
write buffering is minimized.
Perhaps there is no way to easily separate the NFS client case from
the normal page cache behavior?
Simon-
next prev parent reply other threads:[~2004-06-02 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 21:38 NFS client behavior on close Simon Kirby
2004-06-02 6:55 ` Trond Myklebust
2004-06-02 15:41 ` Simon Kirby [this message]
2004-06-02 16:38 ` Trond Myklebust
2004-06-02 19:16 ` Simon Kirby
2004-06-02 19:45 ` Trond Myklebust
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=20040602154146.GA2481@netnation.com \
--to=sim@netnation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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