From: Steve Dickson <SteveD@redhat.com>
To: MINOURA Makoto <minoura@valinux.co.jp>
Cc: nfs@lists.sourceforge.net, taka@valinux.co.jp, yamamoto@valinux.co.jp
Subject: Re: NFSD Flow Control Using the TCP Transport
Date: Fri, 21 Mar 2003 15:38:43 -0500 [thread overview]
Message-ID: <3E7B7853.4020605@RedHat.com> (raw)
In-Reply-To: 20030320042454.496801DA3E6@brer.local.valinux.co.jp
MINOURA Makoto wrote:
>Current implementation closes the socket on EAGAIN/partial
>write, but has some delay. During this delay on-queue
>messages are unintentionally sent (in case the NFS traffic
>is busy). We addressed this problem by removing the delay
>(close the socket immediatly) but sending the remaining
>correctly should be better.
>
So If I understand what your saying, EAGAINs or partial writes are
interpreted
as fatal errors. This confuse me. EAGAINs or partial writes are flow
control
issues not fatal errors. Just like on the client side, shouldn't the
thread sleep until there is room? Closing down the socket seems a
bit drastic... Or am I missing something?
SteveD.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-21 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 15:05 NFSD Flow Control Using the TCP Transport Steve Dickson
2003-03-20 4:24 ` MINOURA Makoto
2003-03-20 4:43 ` MINOURA Makoto
2003-03-21 20:38 ` Steve Dickson [this message]
2003-03-24 2:51 ` MINOURA Makoto
2003-03-24 15:07 ` Steve Dickson
2003-03-25 5:32 ` MINOURA Makoto
2003-03-25 11:33 ` Steve Dickson
2003-03-26 5:07 ` MINOURA Makoto
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=3E7B7853.4020605@RedHat.com \
--to=steved@redhat.com \
--cc=minoura@valinux.co.jp \
--cc=nfs@lists.sourceforge.net \
--cc=taka@valinux.co.jp \
--cc=yamamoto@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.