From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jeff Layton <jlayton@redhat.com>,
"bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@openvz.org" <devel@openvz.org>
Subject: Re: [PATCH v2] SUNRPC: check current nsproxy before set of node name on client creation
Date: Mon, 10 Sep 2012 19:55:34 +0400 [thread overview]
Message-ID: <504E0D76.5060905@parallels.com> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA908F96556@SACEXCMBX04-PRD.hq.netapp.com>
10.09.2012 19:41, Myklebust, Trond пишет:
> On Mon, 2012-09-10 at 19:37 +0400, Stanislav Kinsbursky wrote:
>> Hi, Trond.
>> So, if I understand you right, we can create rpc client (or increase usage
>> counter) on NSMPROC_MON call and destroy (or decrease usage counter) on
>> NSMPROC_UNMON call.
>> Will this solution works?
>
> The rpc client(s) will need to be per-net-namespace, which complicates
> matters a little bit, but yes, creation at NSMPROC_MON, and destruction
> at NSMPROC_UNMON should work.
>
Not really. We already have per-net Lockd data. So, adding one more
reference-counted rpc client doesn't look that complicated.
Ok, thanks. I'll try to implement this.
--
Best regards,
Stanislav Kinsbursky
next prev parent reply other threads:[~2012-09-10 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 11:37 [PATCH v2] SUNRPC: check current nsproxy before set of node name on client creation Stanislav Kinsbursky
2012-08-13 12:10 ` Jeff Layton
2012-09-07 22:32 ` Myklebust, Trond
2012-09-07 22:32 ` Myklebust, Trond
2012-09-08 5:59 ` Stanislav Kinsbursky
2012-09-08 14:33 ` Myklebust, Trond
2012-09-08 14:33 ` Myklebust, Trond
2012-09-10 8:43 ` Stanislav Kinsbursky
2012-09-10 15:27 ` Myklebust, Trond
2012-09-10 15:27 ` Myklebust, Trond
2012-09-10 15:37 ` Stanislav Kinsbursky
2012-09-10 15:41 ` Myklebust, Trond
2012-09-10 15:41 ` Myklebust, Trond
2012-09-10 15:55 ` Stanislav Kinsbursky [this message]
2012-09-13 12:11 ` Stanislav Kinsbursky
2012-09-13 13:30 ` Myklebust, Trond
2012-09-13 13:30 ` Myklebust, Trond
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=504E0D76.5060905@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=devel@openvz.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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 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.