On Fri, Sep 11, 2009 at 06:52:55PM -0400, andros@xxxxxxxxxx wrote: > From: Andy Adamson <andros@xxxxxxxxxx> > > Both the max request and the max response size include the RPC header with > credential (request only) and verifier as well as the payload. > > The RPCSEC_GSS credential and verifier are the largest. Kerberos is the only > supported GSS security mechansim, so the Kerberos GSS credential and verifier > sizes are used. Rather than trying to estimate this is might be simplest just to use what the server's using to allocate memory: RPCSVC_MAXPAGES. No, that also takes into account space for the reply. You could do PAGE_SIZE * (1 + (RPCSVC_MAXPAYLOAD+PAGE_SIZE-1)/PAGE_SIZE) Actually, by design the server's real limit is actually on the sum of the request and the reply sizes. What happens if we get a request such that both the request and reply are under our advertised limits, but the sum is too much? Can we just declare that no client will be that weird and that we shouldn't have to worry about it? --b. -- 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
