public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	Dr James Bruce Fields <bfields@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Pavel Emelianov <xemul@parallels.com>,
	"neilb@suse.de" <neilb@suse.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"devel@openvz.org" <devel@openvz.org>
Subject: Re: [PATCH 0/5] SUNRPC: make caches network namespace aware
Date: Thu, 19 Jan 2012 10:47:31 -0500	[thread overview]
Message-ID: <20120119154731.GB527@fieldses.org> (raw)
In-Reply-To: <4F18376C.9090504@parallels.com>

On Thu, Jan 19, 2012 at 07:31:56PM +0400, Stanislav Kinsbursky wrote:
> 19.01.2012 19:19, Trond Myklebust пишет:
> >On Thu, 2012-01-19 at 18:48 +0400, Stanislav Kinsbursky wrote:
> >>One more step towards to "NFS in container".
> >>With this patch set caches are allocated per network namespace.
> >>
> >>The following series consists of:
> >>
> >>---
> >>
> >>Stanislav Kinsbursky (5):
> >>       SUNRPC: cache creation and destruction routines introduced
> >>       SUNRPC: create unix gid cache per network namespace
> >>       SUNRPC: create GSS auth cache per network namespace
> >>       SUNRPC: ip map cache per network namespace cleanup
> >>       SUNRPC: generic cache register routines removed
> >
> >The patches look good, and I've applied them for now in my 'devel'
> >branch so we can test them, but I'd like to get an Ack/Nack from Bruce
> >before committing to merging them.
> >
> 
> Cool, thanks.
> BTW, these patches depends on patch "NFSd: use
> network-namespace-aware cache registering routines", which Bruce
> took already (and it's even in linux-next already), but not in your
> devel tree for some reason.

And Linus has pulled those, so if Trond bases his tree on -rc1, he'll
have "NFSd: use network-namespace-aware cache registering routines".

You know best what you're planning to submit over the next cycle, and
what the dependencies are, and which side (client or server) it's likely
to touch more.  So, your choice, I think.  If necessary Trond and I can
probably do a merge between us at some point.

Either way, I'll go take a look at them now....--b.

--b.

  parent reply	other threads:[~2012-01-19 15:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 14:48 [PATCH 0/5] SUNRPC: make caches network namespace aware Stanislav Kinsbursky
2012-01-19 14:49 ` [PATCH 1/5] SUNRPC: cache creation and destruction routines introduced Stanislav Kinsbursky
2012-01-19 14:49 ` [PATCH 2/5] SUNRPC: create unix gid cache per network namespace Stanislav Kinsbursky
2012-01-19 16:24   ` J. Bruce Fields
2012-01-19 17:00     ` Stanislav Kinsbursky
2012-01-19 14:49 ` [PATCH 3/5] SUNRPC: create GSS auth " Stanislav Kinsbursky
2012-01-19 16:31   ` J. Bruce Fields
2012-01-19 17:04     ` Stanislav Kinsbursky
2012-01-19 17:40       ` J. Bruce Fields
2012-01-19 17:51         ` Stanislav Kinsbursky
2012-01-19 14:49 ` [PATCH 4/5] SUNRPC: ip map cache per network namespace cleanup Stanislav Kinsbursky
2012-01-19 16:37   ` J. Bruce Fields
2012-01-19 17:10     ` Stanislav Kinsbursky
2012-01-19 22:21       ` J. Bruce Fields
2012-01-19 14:49 ` [PATCH 5/5] SUNRPC: generic cache register routines removed Stanislav Kinsbursky
2012-01-19 15:19 ` [PATCH 0/5] SUNRPC: make caches network namespace aware Trond Myklebust
2012-01-19 15:31   ` Stanislav Kinsbursky
2012-01-19 15:34     ` Myklebust, Trond
2012-01-19 15:43       ` Stanislav Kinsbursky
2012-01-19 15:47     ` bfields [this message]
2012-01-19 16:01       ` Stanislav Kinsbursky
2012-01-19 17:34       ` Myklebust, Trond
2012-01-19 22:40   ` J. Bruce Fields
2012-01-19 17:14 ` Stanislav Kinsbursky

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=20120119154731.GB527@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@redhat.com \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=jbottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=skinsbursky@parallels.com \
    --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