public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
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 15:26:37 +0200	[thread overview]
Message-ID: <4BB49F0D.80009@s3group.cz> (raw)
In-Reply-To: <1270127869.3533.12.camel@localhost.localdomain>

Hi Trond,

Does it have anything to do with the situation when we want an the same 
filesystem to be mounted twice somewhere else with a different flags? 
(i.e. RO/RW for example)
If yes, I remember some discussion about it in the past (the above was 
not possible).
Thanks,

Ondrej
> Look again at nfs_init_server_rpcclient(). The pseudoflavour is not the
> only thing that is changed. We also change the soft flag and the timeout
> properties of the server->client.
>
> The point is that users sometimes want to specify per-mountpoint
> transport properties, and so we try to give them that possibility, while
> at the same time sharing sockets/rdma connections.
>
> Cheers
>   Trond
>
> _______________________________________________
> NFSv4 mailing list
> NFSv4@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
>   

  reply	other threads:[~2010-04-01 13:26 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 [this message]
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

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=4BB49F0D.80009@s3group.cz \
    --to=webserv@s3group.cz \
    --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