linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [RFC 19/21] NFS: Convert v4 into a module
Date: Mon, 13 Feb 2012 01:05:25 +0200	[thread overview]
Message-ID: <4F3845B5.6020402@panasas.com> (raw)
In-Reply-To: <1329085229.2746.3.camel@lade.trondhjem.org>

On 02/13/2012 12:20 AM, Myklebust, Trond wrote:
> On Sun, 2012-02-12 at 20:02 +0200, Boaz Harrosh wrote:
>> On 02/11/2012 12:02 AM, bjschuma@netapp.com wrote:
>>> The module will be created in the same directory as nfs.ko.  You need to
>>> run `modprobe nfs4` before you can use it.
>>>
>>
>> Can we do this mod_alias and autoloading magic like we do with 
>> LD drivers, so if NFSv4 is requested it is automatically loaded
>> by Kernel. 
> 
> You need to call request-module() from the nfs.ko module as soon as you
> know which version the user is trying to load...
> I don't see why you need mod_alias?
> 

That will work. I can now see that it's on the todo in the [00/21] mail
Sorry for the noise

Thanks
Boaz

  reply	other threads:[~2012-02-12 23:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 22:01 [RFC 00/21] NFS: Create NFS Modules bjschuma
2012-02-10 22:01 ` [RFC 02/21] NFS: Make v2 configurable bjschuma
2012-02-10 22:01 ` [RFC 03/21] NFS: Add version registering framework bjschuma
2012-02-10 22:01 ` [RFC 04/21] NFS: Convert v2 into a module bjschuma
2012-02-10 22:01 ` [RFC 05/21] NFS: Break up the nfs_fs_mount function bjschuma
2012-02-10 22:01 ` [RFC 06/21] NFS: Create a single nfs_clone_super() function bjschuma
2012-02-10 22:01 ` [RFC 07/21] NFS: Version specific xdev mounting bjschuma
2012-02-10 22:01 ` [RFC 08/21] NFS: Only initialize the ACL client in the v3 case bjschuma
2012-02-10 22:01 ` [RFC 09/21] NFS: Convert v3 into a module bjschuma
2012-02-10 22:01 ` [RFC 10/21] NFS: Initialize NFS v4 from nfs4super.c bjschuma
2012-02-10 22:01 ` [RFC 11/21] NFS: Move lots of code from super.c bjschuma
2012-02-10 22:01 ` [RFC 12/21] NFS: module-specific submount function bjschuma
2012-02-10 22:01 ` [RFC 13/21] NFS: Custom alloc and free client functions for modules bjschuma
2012-02-10 22:01 ` [RFC 14/21] NFS: Move nfs4_set_client() and support code to nfs4client.c bjschuma
2012-02-10 22:01 ` [RFC 15/21] NFS: Move the nfs4_init_client() " bjschuma
2012-02-10 22:02 ` [RFC 16/21] NFS: Move the v4 getroot code to nfs4getroot.c bjschuma
2012-02-10 22:02 ` [RFC 17/21] NFS: Deal with delegations bjschuma
2012-02-10 22:02 ` [RFC 18/21] NFS: Use the IS_ENABLED macro for CONFIG_NFS_V4 bjschuma
2012-02-10 22:02 ` [RFC 19/21] NFS: Convert v4 into a module bjschuma
2012-02-12 18:02   ` Boaz Harrosh
2012-02-12 22:20     ` Myklebust, Trond
2012-02-12 23:05       ` Boaz Harrosh [this message]
2012-02-13 13:29         ` Bryan Schumaker
2012-02-10 22:02 ` [RFC 20/21] Export symbols for v4 module bjschuma
2012-02-10 22:02 ` [RFC 21/21] NFS: Export v4.1 symbols back to nfs.ko bjschuma

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=4F3845B5.6020402@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Bryan.Schumaker@netapp.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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).