Hi Bruce- On Jul 10, 2014, at 2:49 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > On Thu, Jul 10, 2014 at 02:24:57PM -0400, Chuck Lever wrote: >> >> On Jul 10, 2014, at 2:19 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: >> >>> On Thu, Jul 10, 2014 at 01:44:35PM -0400, Chuck Lever wrote: >>>> The server should comply with RFC 5667, >>> >>> Where's the relevant language? (I took a quick look but didn't see it.) >> >> Sorry, I listed the wrong RFC when I wrote the description of bug 246. >> It’s actually RFC 5666, section 3.7. > > Thanks. > >>> So I think you just want to drop the round-up of len, not the whole >>> check. >> >> I’ll try that, thanks! Works-as-expected. > Actually, I'd really rather this get fixed up in the rpc layer. The > padding is really required for correct xdr. How so? All of NFSv4 and all other NFSv3 operations work as expected without that padding present. There doesn’t seem to be any operational dependency on the presence of padding. Help? > The fact that RDMA doesn't > require those zeroes to be literally transmitted across the network > sounds like a transport-level detail that should be hidden from the xdr > code. The best I can think of is adding a false page array entry to the xdr_buf if the last incoming page is short by a few bytes. -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
