From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Chuck Lever <cel@citi.umich.edu>, <nfs@lists.sourceforge.net>
Subject: Re: Re: PATCH - RPC/TCP 2 of 4 - Allow SO_REUSEADDR for NFS sockets
Date: 14 Aug 2002 03:17:15 +0200 [thread overview]
Message-ID: <shsvg6ensro.fsf@charged.uio.no> (raw)
In-Reply-To: <15704.41158.32143.348415@notabene.cse.unsw.edu.au>
>>>>> " " == Neil Brown <neilb@cse.unsw.edu.au> writes:
>> it's been suggested that the client should also try reusing the
>> port number when reconnecting over TCP... any thoughts on that?
> Why? You would not be able to reconnect until the TCP timeout
> on connection re-use has passed, and by that time any benefit
> that you might gain is probably lost. How does the TCP timeout
> compare with the replay-cache timeout??
The connection may break for other reasons (network partition for
instance). Reusing the port number guarantees that the replay cache
works as expected.
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-08-14 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 2:57 PATCH - RPC/TCP 2 of 4 - Allow SO_REUSEADDR for NFS sockets Neil Brown
2002-08-13 3:23 ` Chuck Lever
2002-08-13 6:01 ` Neil Brown
2002-08-14 1:04 ` Julian Cowley
2002-08-14 1:17 ` Trond Myklebust [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=shsvg6ensro.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=cel@citi.umich.edu \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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.