On Thu, Aug 24, 2006 at 04:37:11PM +1000, NeilBrown wrote:
> The limit over UDP remains at 32K. Also, make some of
> the apparently arbitrary sizing constants clearer.
>
> The biggest change here involves replacing NFSSVC_MAXBLKSIZE
> by a function of the rqstp. This allows it to be different
> for different protocols (udp/tcp) and also allows it
> to depend on the servers declared sv_bufsiz.
>
> Note that we don't actually increase sv_bufsz for nfs yet.
> That comes next.
This patch has some problems. (Apologies for being so slow to look at
them!)
We're reporting svc_max_payload(rqstp) as the server's maximum
read/write block size:
> @@ -538,15 +539,16 @@ nfsd3_proc_fsinfo(struct svc_rqst * rqst
> struct nfsd3_fsinfores *resp)
> {
> int nfserr;
> + u32 max_blocksize = svc_max_payload(rqstp);
>
> dprintk("nfsd: FSINFO(3) %s\n",
> SVCFH_fmt(&argp->fh));
>
> - resp->f_rtmax = NFSSVC_MAXBLKSIZE;
> - resp->f_rtpref = NFSSVC_MAXBLKSIZE;
> + resp->f_rtmax = max_blocksize;
> + resp->f_rtpref = max_blocksize;
> resp->f_rtmult = PAGE_SIZE;
> - resp->f_wtmax = NFSSVC_MAXBLKSIZE;
> - resp->f_wtpref = NFSSVC_MAXBLKSIZE;
> + resp->f_wtmax = max_blocksize;
> + resp->f_wtpref = max_blocksize;
> resp->f_wtmult = PAGE_SIZE;
> resp->f_dtpref = PAGE_SIZE;
> resp->f_maxfilesize = ~(u32) 0;
But svc_max_payload() usually returns sv_bufsz in the TCP case:
> +u32 svc_max_payload(const struct svc_rqst *rqstp)
> +{
> + int max = RPCSVC_MAXPAYLOAD_TCP;
> +
> + if (rqstp->rq_sock->sk_sock->type == SOCK_DGRAM)
> + max = RPCSVC_MAXPAYLOAD_UDP;
> + if (rqstp->rq_server->sv_bufsz < max)
> + max = rqstp->rq_server->sv_bufsz;
> + return max;
> +}
That's the *total* size of the buffer for holding requests and replies.
If a client actually tries to send a write of that size, the entire
request will of course exceed sv_bufsz, so we'll drop it. (We've seen
this happen with the Solaris v4 client.)
> -#define NFSD_BUFSIZE (1024 + NFSSVC_MAXBLKSIZE)
> +/*
> + * Largest number of bytes we need to allocate for an NFS
> + * call or reply. Used to control buffer sizes. We use
> + * the length of v3 WRITE, READDIR and READDIR replies
> + * which are an RPC header, up to 26 XDR units of reply
> + * data, and some page data.
> + *
> + * Note that accuracy here doesn't matter too much as the
> + * size is rounded up to a page size when allocating space.
> + */
Is the rounding up *always* going to increase the size? And if not,
then why doesn't accuracy matter?
> +#define NFSD_BUFSIZE ((RPC_MAX_HEADER_WITH_AUTH+26)*XDR_UNIT + NFSSVC_MAXBLKSIZE)
I think this results in 80 less bytes less than before, I think.
No doubt we have lots of wiggle room here, but I'd rather we didn't
decrease that size without seeing a careful analysis.
--b.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
