linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Pavel Emelianov <xemul@parallels.com>,
	"Kirill A. Shutemov" <kas@openvz.org>,
	"jlayton@redhat.com" <jlayton@redhat.com>
Subject: Re: network-namespace-aware nfsd
Date: Fri, 07 Oct 2011 14:18:56 +0400	[thread overview]
Message-ID: <4E8ED210.1030506@parallels.com> (raw)
In-Reply-To: <20111006164632.GC21627@fieldses.org>

06.10.2011 20:46, J. Bruce Fields пишет:
> On Thu, Oct 06, 2011 at 01:59:09PM +0400, Stanislav Kinsbursky wrote:
>> 05.10.2011 22:19, J. Bruce Fields пишет:
>>> To start with I suspect it would be OK to share the one lockd thread.
>>>
>>
>> Yep, I think so too. It just will be harder to implement.
>
> Why do you think it will be harder to implement?
>

Because making lockd kthread per net ns is very easy. :)

> There may be something about how tasks and namespaces interact that I'm
> missing here....
>

The main problem, as I see it now, is creating and especially destroying lockd 
rpcbind clients (and per ns data) on CT stop.
Right now they are destroyed on lockd kthread exit. And we can't make this 
destruction in per-net operations since those clients holds net ns.
Thus, nlmclnt_init(done) logic have to be significantly reworked.

> To me it seems like either way we're going to have to add the network
> namespace as an argument to any data structure lookups that we're doing,
> and it doesn't really matter whether we get the namespace out of the
> svc_rqst or someplace else.
>

Yep, seems the same to me.

> --b.


-- 
Best regards,
Stanislav Kinsbursky

      reply	other threads:[~2011-10-07 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 15:02 network-namespace-aware nfsd J. Bruce Fields
2011-10-05 17:26 ` Stanislav Kinsbursky
2011-10-05 18:19   ` J. Bruce Fields
2011-10-06  9:59     ` Stanislav Kinsbursky
2011-10-06 12:29       ` Pavel Emelyanov
2011-10-06 13:11         ` J. Bruce Fields
2011-10-06 13:14           ` Pavel Emelyanov
2011-10-06 13:18             ` Stanislav Kinsbursky
2011-10-06 16:46       ` J. Bruce Fields
2011-10-07 10:18         ` Stanislav Kinsbursky [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=4E8ED210.1030506@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=kas@openvz.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xemul@parallels.com \
    /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;
as well as URLs for NNTP newsgroup(s).