From: Ben Greear <greearb@candelatech.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
trond@netapp.com, Pavel Emelianov <xemul@parallels.com>
Subject: Re: NFS client virtualization plan
Date: Tue, 16 Aug 2011 04:59:06 -0700 [thread overview]
Message-ID: <4E4A5B8A.5060802@candelatech.com> (raw)
In-Reply-To: <4E4A4FA9.7080600@parallels.com>
On 08/16/2011 04:08 AM, Stanislav Kinsbursky wrote:
> Added maintainer to mail recipients.
> Trond, please, have a look.
> Sorry for inconvenience.
I have a set of patches that let NFS clients bind to a specific IP
address, but I haven't gotten any feedback in the month since
I posted them.
But, likely you will want to touch similar paths to what I touched.
Here's my patch series:
https://lkml.org/lkml/2011/7/15/382
You need some patches to mount.nfs
for full functionality, in case you want to try it out:
https://github.com/greearb/nfs-utils-ct
Thanks,
Ben
>
> 16.08.2011 15:00, Stanislav Kinsbursky пишет:
>> Hello.
>> I'm going to virtualize NFS in mainline and here is my plan for NFS client part.
>> Any suggestions or criticism are welcome.
>>
>> ==============================================================================
>>
>> "NFS client" virtualization plan:
>>
>> _RPC layer_:
>>
>> 1) Make rpcbind clients (rpcb_local_clnt and rpcb_local4_clnt) to be
>> per net namespace.
>>
>> _NFS layer_:
>>
>> 1) Net namespace inheritance (current->nsproxy->net have to be used instead
>> of init_net).
>> Pointer to net namespace can be stored on nfs_client structure, which will
>> give easy access to proper net namespace during RPC transports creation.
>>
>> 2) Make Lockd kthread able to handle requests from different net namespaces.
>>
>> 3) Make NFS callbacks kthreads (nfs4_callback_svc and nfs4.1_callback_svc) able
>> to handle requests from different net namespaces.
>>
>> 4) Make NFS info lists (nfs_volume_list and nfs_client_list) to be per
>> net namespace in addition to global ones.
>>
>> 5) Make NFS proc variables and it's internal content variables to be per
>> net namespace in addition to global ones.
>>
>> 6) Make NFS sysctl variables and it's internal content variables to be per
>> net namespace in addition to global ones.
>>
>>
>>
>
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-08-16 12:00 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 [this message]
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
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=4E4A5B8A.5060802@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.com \
--cc=trond@netapp.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