From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Ian Kent <raven@themaw.net>, Charles Lever <cel@citi.umich.edu>,
nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fix xprt_bindresvport range
Date: Fri, 25 Feb 2005 10:28:09 +0100 [thread overview]
Message-ID: <20050225092809.GD15249@suse.de> (raw)
In-Reply-To: <1109268742.11433.14.camel@lade.trondhjem.org>
On Thu, Feb 24, 2005 at 10:12:22AM -0800, Trond Myklebust wrote:
> It is needed in the kernel if you want to use connection pools in order
> to make disconnection and port re-use fast. Fast port re-use is also
> needed in order to deal with idempotency issues when the TCP connection
> fails (the server replay cache is usually indexed on the port number).
Is the whole nfsd cache still that important for TCP connections?
It's mostly useless with multi-homing, it will become even more so if we
ever do load balancing across multiple TCP connections... Indexing
by network protocol information is broken beyond fixing, and the only
way to salvage the cache for TCP is to start indexing it differently
(eg based on a hash of parts of the RPC header and creds)
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-25 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 16:28 [PATCH] Fix xprt_bindresvport range Olaf Kirch
2005-02-23 16:35 ` Trond Myklebust
2005-02-24 2:59 ` Ian Kent
2005-02-24 4:23 ` Trond Myklebust
2005-02-24 10:14 ` Olaf Kirch
2005-02-24 18:12 ` Trond Myklebust
2005-02-25 9:28 ` Olaf Kirch [this message]
2005-02-25 17:30 ` Trond Myklebust
2005-02-28 11:33 ` Olaf Kirch
2005-02-25 0:54 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2005-02-23 17:05 Lever, Charles
2005-02-28 16:41 Lever, Charles
2005-02-28 16:57 ` Olaf Kirch
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=20050225092809.GD15249@suse.de \
--to=okir@suse.de \
--cc=cel@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
--cc=raven@themaw.net \
--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 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.