> > > >> If you print ch_count, it is 2 for NFS WRITEs from a Linux client, > >> no matter how large the write payload is. Therefore I think the check > >> as it is written is not particularly useful. > > > > Why are there 2? > > The first chunk lists the pages the server is to read, and the second > chunk has the zero pad for XDR alignment. > > If pad optimization is enabled on the client, there is just 1 chunk in > the RPC's Read list. > So the code as it stands violates the RFC by sending 2 chunks? And if I change the server to only consume 1, then everything unaligned will break? -- 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
