[pnfs] [PATCH 0/8] nfsd: convert xdr x-coding to use function vectors

[J. Bruce Fields]

On Tue, Jul 01, 2008 at 12:08:45AM +0300, Benny Halevy wrote:
> J. Bruce Fields wrote:
> > OK.  I'm assuming we should wait to start applying nfsv4.1 specific
> > patches till we have enough patches ready to provide some minimal 4.1
> > functionality.
> 
> Absolutely.
> 
> The whole patchset has minimal functionality and is now backward
> compatible (i.e. 4.1 should work against 2, 3, 4, and 4.1 servers,
> 4.1 server works against 2, 3, 4, and 4.1 clients.  testing
> was focused on 4.0 x 4.1)

Sounds good!

> Next step is cleaning up the patches for review, then I'll
> send a series of patchsets comprising the full functionality.
> 
> I'm still nto sure what would be clearer, send each feature
> as client/server pairs, or send the full series for the server
> side, then the client's.

The only considerations I can think of are:

	- Stuff tends to fall through the cracks when it's not
	  immediately obvious which of my or Trond's tree it's being
	  submitted to.  For anything that really has to be mixed
	  together, we'll figure something out, but for the rest it'd be
	  nice if a single patch series always went to just one of us.

	- We want rough parity between the client and server; it'd be
	  great if we could always test new features in the 2.6.x server
	  using the 2.6.x client (and vice-versa).  But if one lags by a
	  version I don't suppose it'll be a huge deal.

Beyond that--I'm not really sure what to suggest.

--b.


> 
> > 
> >> 	(currently placed early in the series on my private tree)
> > 
> > OK.  Looks like they'll follow the introduction of the new CONFIG option
> > at least?
> 
> Of course.
> They follow the CONFIG option and some basic type and constant definitions.
> 
> Benny
> 
> > 
> > --b.
> > 
> >> 	xdr stubs implement the nfs41 decoders in a vecotr of their own.
>