linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC 0/4] NFS: Modularize NFS v3
@ 2011-12-01 16:48 bjschuma
  2011-12-01 16:48 ` [RFC v2 1/4] NFS: Export symbols needed by an NFS v3 module bjschuma
                   ` (6 more replies)
  0 siblings, 7 replies; 20+ messages in thread
From: bjschuma @ 2011-12-01 16:48 UTC (permalink / raw)
  To: Trond.Myklebust; +Cc: linux-nfs, Bryan Schumaker

From: Bryan Schumaker <bjschuma@netapp.com>

This set of patches removes NFS v3 from the main NFS kernel module and creates
a new module containing the proc, xdr, and acl code.  This will give us a
single directory to put NFS v3 specific code so it doesn't need to be mixed in
with the generic client stuff.

I'm sure this could still use a lot of work, but I figured I would wait to see
what everybody thinks first.  I imagine that once we get an "nfs submodule"
system working it'll be easier to convert v2 and v4 (and possibly v4.1?) to
modules.

I split the second patch into two to make it easier to see what my changes were
to get everything to compile.  Hopefully this will save some pain in having to
look through 7000+ line patch that resulted from my `mv nfs3*.c nfs3/`
command.  I can combine everything in a future version of the patch.

v2:
  - I set the "diff.renames copy" git config option to create a smaller second
    patch.  Maybe this time it won't get me kicked off the mailing list...
    Thanks to Boaz and Jim for the tip!

Thoughts?

- Bryan


^ permalink raw reply	[flat|nested] 20+ messages in thread
* [RFC 0/4] NFS: Modularize NFS v3
@ 2011-11-22 22:57 bjschuma
  2011-11-23  2:19 ` Boaz Harrosh
  2011-11-23 18:27 ` J. Bruce Fields
  0 siblings, 2 replies; 20+ messages in thread
From: bjschuma @ 2011-11-22 22:57 UTC (permalink / raw)
  To: Trond.Myklebust; +Cc: linux-nfs, Bryan Schumaker

From: Bryan Schumaker <bjschuma@netapp.com>

This set of patches removes NFS v3 from the main NFS kernel module and creates
a new module containing the proc, xdr, and acl code.  This will give us a
single directory to put NFS v3 specific code so it doesn't need to be mixed in
with the generic client stuff.

I'm sure this could still use a lot of work, but I figured I would wait to see
what everybody thinks first.  I imagine that once we get an "nfs submodule"
system working it'll be easier to convert v2 and v4 (and possibly v4.1?) to
modules.

I split the second patch into two to make it easier to see what my changes were
to get everything to compile.  Hopefully this will save some pain in having to
look through 7000+ line patch that resulted from my `mv nfs3*.c nfs3/`
command.  I can combine everything in a future version of the patch.

Thoughts?

- Bryan


^ permalink raw reply	[flat|nested] 20+ messages in thread

end of thread, other threads:[~2012-01-10 17:58 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-01 16:48 [RFC 0/4] NFS: Modularize NFS v3 bjschuma
2011-12-01 16:48 ` [RFC v2 1/4] NFS: Export symbols needed by an NFS v3 module bjschuma
2011-12-01 16:48 ` [RFC v2 2/4] NFS: Move the NFS v3 code into its own subdirectory bjschuma
2011-12-01 16:48 ` [RFC v2 3/4] NFS: Add functions for adding new NFS versions bjschuma
2011-12-01 16:48 ` [RFC v2 4/4] NFS: Turn NFS v3 into a module bjschuma
2011-12-01 17:36 ` [RFC 0/4] NFS: Modularize NFS v3 Jim Rees
2011-12-01 19:56   ` Bryan Schumaker
2011-12-01 21:05 ` Steve Dickson
2011-12-01 21:55   ` Bryan Schumaker
2011-12-01 21:57     ` Trond Myklebust
2011-12-02  2:38       ` Steve Dickson
2011-12-02  2:01     ` Steve Dickson
2011-12-02 16:24       ` J. Bruce Fields
2012-01-10 17:42 ` Stanislav Kinsbursky
2012-01-10 17:58   ` Bryan Schumaker
  -- strict thread matches above, loose matches on Subject: below --
2011-11-22 22:57 bjschuma
2011-11-23  2:19 ` Boaz Harrosh
2011-11-23  2:41   ` Jim Rees
2011-11-28 14:14     ` Bryan Schumaker
2011-11-23 18:27 ` J. Bruce Fields

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).