On Thu Dec 1 16:05:03 2011, Steve Dickson wrote: > > > On 12/01/2011 11:48 AM, bjschuma@xxxxxxxxxx wrote: >> From: Bryan Schumaker <bjschuma@xxxxxxxxxx> >> >> 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? > Now what is the motivating reason behind this re-architecture > other than making the upstream kernel literally impossible to > back port to older kernels?? > I wasn't thinking about backporting when I did this... is there a better way to do this that wouldn't make it a pain to backport? My thought was that it would help clean things up a bit by adding a bit of separation between the nfs client and each nfs protocol. It would also allow user to decide what they need at run time rather than at compile time. > steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
