From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: why does each NFS mount have (at least) 2 rpc_clnt's ?
Date: Thu, 01 Apr 2010 14:00:48 -0400 [thread overview]
Message-ID: <1270144848.3533.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20100401132619.24278811@barsoom.rdu.redhat.com>
On Thu, 2010-04-01 at 13:26 -0400, Jeff Layton wrote:
> That said, I still am not certain I see why we want to have an rpc_clnt
> that's shared between the mounts though clearly there's benefit to
> sharing the xprt between them.
Sharing the xprt is by far the main (and most important) benefit.
Without it, we would have the same mess with running out of privileged
port numbers that we had with the 2.4.x series.
Cheers
Trond
prev parent reply other threads:[~2010-04-01 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 12:46 why does each NFS mount have (at least) 2 rpc_clnt's ? Jeff Layton
2010-04-01 13:17 ` Trond Myklebust
2010-04-01 13:26 ` Ondrej Valousek
2010-04-01 14:07 ` Trond Myklebust
2010-04-01 14:12 ` Ondrej Valousek
2010-04-01 17:26 ` Jeff Layton
2010-04-01 18:00 ` 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=1270144848.3533.27.camel@localhost.localdomain \
--to=trond.myklebust@fys.uio.no \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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