All of lore.kernel.org
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Jeff Layton <jlayton@redhat.com>
Subject: Re: [RFC] NFSd laundromat containerization
Date: Fri, 11 May 2012 09:53:07 -0400	[thread overview]
Message-ID: <20120511135306.GA12795@fieldses.org> (raw)
In-Reply-To: <4FAD1934.8070908@parallels.com>

On Fri, May 11, 2012 at 05:50:44PM +0400, Stanislav Kinsbursky wrote:
> Hello.
> I'm currently looking on NFSd laundromat work, and it looks like
> have to be performed per networks namespace context.
> It's easy to make corresponding delayed work per network namespace
> and thus gain per-net data pointer in laundromat function.
> But here a problem appears: network namespace is required to skip
> clients from other network namespaces while iterating over global
> lists (client_lru and friends).
> I see two possible solutions:
> 1) Make these list per network namespace context. In this case
> network namespace will not be required - per-net data will be
> enough.
> 2) Put network namespace link on per-net data (this one is easier, but uglier).

I'd rather there be as few shared data structures between network
namespaces as possible--I think that will simplify things.

So, of those two choices, #1.

--b.

  reply	other threads:[~2012-05-11 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 13:50 [RFC] NFSd laundromat containerization Stanislav Kinsbursky
2012-05-11 13:53 ` bfields [this message]
2012-05-11 14:02   ` Jeff Layton
2012-05-11 14:15     ` Stanislav Kinsbursky
2012-05-11 15:09       ` bfields
2012-05-12  8:59   ` Stanislav Kinsbursky
2012-05-12 14:16     ` bfields
2012-05-12 14:40       ` Stanislav Kinsbursky
2012-05-14  9:00       ` Stanislav Kinsbursky
2012-05-14 10:19         ` Stanislav Kinsbursky
2012-05-15 13:40         ` Jeff Layton
2012-05-15 13:55           ` Jeff Layton

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=20120511135306.GA12795@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@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 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.