From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steven <steven@void.org>
Cc: Peter Staubach <staubach@redhat.com>, nfs@lists.sourceforge.net
Subject: Re: Minor problem in nfsv3 write
Date: Tue, 20 Sep 2005 15:26:40 -0400 [thread overview]
Message-ID: <20050920192640.GD31948@fieldses.org> (raw)
In-Reply-To: <20050920183054.BCB62F4@dead.void.org>
On Tue, Sep 20, 2005 at 11:30:54AM -0700, Steven wrote:
> I agree. I don't think it is a good policy to tell the client that all
> of the data was written when some was not.
>
> For what it's worth, the RFC says that if the write size exceeds wtmax
> then the server may write only wtmax bytes of the request.
OK. Could you regenerate that patch with diff -up? (See
Documentation/SubmittingPatches.) Don't bother sending the modified
function, it's the patch that people want.
--b.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-09-20 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 1:10 Minor problem in nfsv3 write Steven
2005-09-20 1:25 ` J. Bruce Fields
2005-09-20 12:25 ` Peter Staubach
2005-09-20 18:30 ` Steven
2005-09-20 19:26 ` J. Bruce Fields [this message]
2005-09-20 22:19 ` [PATCH] " Steven
2005-09-20 23:46 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 6:29 Sumeet Gupta
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=20050920192640.GD31948@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=staubach@redhat.com \
--cc=steven@void.org \
/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