Linux NFS development
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Pavel Emelianov <xemul@parallels.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS client virtualization plan
Date: Mon, 22 Aug 2011 21:30:09 +0400	[thread overview]
Message-ID: <4E529221.6010102@parallels.com> (raw)
In-Reply-To: <20110819193259.GC1641@fieldses.org>

19.08.2011 23:32, J. Bruce Fields =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
> On Fri, Aug 19, 2011 at 09:21:16PM +0400, Stanislav Kinsbursky wrote:
>> Actually, yes, I do. Thanks for notice.
>> Kernel NSM monitor routines will be virtualized.
>> For idmapd and gssd rpc_pipefs virtualization is required.
>> I wasn't going to virtualize rpc_pipefs for now - it was planned to =
be a part of NFS server virtualization, which is planned to be done aft=
er NFS client virtualization.
>
> You'll need rpc_pipefs for gssd and the old idmapd.
>
> Also the new idmapper uses request_key.  I think there's a little
> discussion about this in the archives.
>

Thanks, Bruce.
Nice to know, that you noticed this discussion.
I'll rpc_pipefs to the todo list for NFS client.

--=20
Best regards,
Stanislav Kinsbursky

  reply	other threads:[~2011-08-22 17:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 11:00 NFS client virtualization plan Stanislav Kinsbursky
2011-08-16 11:08 ` Stanislav Kinsbursky
2011-08-16 11:59   ` Ben Greear
2011-08-16 12:19     ` Stanislav Kinsbursky
2011-08-18 15:54 ` Chuck Lever
2011-08-19  9:46   ` Stanislav Kinsbursky
2011-08-19 16:12     ` Chuck Lever
2011-08-19 17:21       ` Stanislav Kinsbursky
2011-08-19 19:32         ` J. Bruce Fields
2011-08-22 17:30           ` Stanislav Kinsbursky [this message]
2011-08-22 18:54             ` Jim Rees

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=4E529221.6010102@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --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