From: Greg Banks <gnb@melbourne.sgi.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Oliver Tennert <tennert@science-computing.de>,
linux-kernel@vger.kernel.org,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: PATCH [NFSd] NFSv3/TCP
Date: Fri, 07 May 2004 17:22:24 +1000 [thread overview]
Message-ID: <409B3930.9B0C9659@melbourne.sgi.com> (raw)
In-Reply-To: 16539.12572.90447.543633@cse.unsw.edu.au
Neil Brown wrote:
>
> There was once a patch floating around which allowed a larger
> NFSSVC_MAXBLKSIZE on architectures with large page sizes, but it never
> got properly submitted I think.
Then please consider this a resend. I'll appreciate any guidance
about proper submission.
This patch has been in SGI's ProPack kernel for 6 months and resulted
in a significant improvement in NFS throughput at a number of customer
sites.
--- /usr/tmp/TmpDir.16250-0/linux/linux/include/linux/nfsd/const.h_1.5 Fri May 7
17:20:22 2004
+++ /usr/tmp/TmpDir.16250-0/linux/linux/include/linux/nfsd/const.h Fri May 7
17:20:22 2004
@@ -12,6 +12,7 @@
#include <linux/nfs.h>
#include <linux/nfs2.h>
#include <linux/nfs3.h>
+#include <asm/page.h>
/*
* Maximum protocol version supported by knfsd
@@ -19,9 +20,16 @@
#define NFSSVC_MAXVERS 3
/*
- * Maximum blocksize supported by daemon currently at 8K
+ * Maximum blocksize supported by daemon. We want the largest
+ * value which 1) fits in a UDP datagram less some headers
+ * 2) is a multiple of page size 3) can be successfully kmalloc()ed
+ * by each nfsd.
*/
-#define NFSSVC_MAXBLKSIZE (8*1024)
+#if PAGE_SIZE > (16*1024)
+#define NFSSVC_MAXBLKSIZE (32*1024)
+#else
+#define NFSSVC_MAXBLKSIZE (2*PAGE_SIZE)
+#endif
#ifdef __KERNEL__
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2004-05-07 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 6:39 PATCH [NFSd] NFSv3/TCP Oliver Tennert
2004-05-07 6:47 ` Neil Brown
2004-05-07 7:19 ` Oliver Tennert
2004-05-07 7:22 ` Greg Banks [this message]
2004-05-07 7:52 ` Oliver Tennert
2004-05-07 8:11 ` Greg Banks
2004-05-07 8:33 ` Strange Linux behaviour!? Oliver Pitzeier
2004-05-07 8:34 ` Christoph Hellwig
2004-05-07 9:01 ` Oliver Pitzeier
2004-05-07 17:25 ` Timothy Miller
2004-05-07 18:21 ` DervishD
2004-05-07 8:43 ` Keith Owens
2004-05-07 10:28 ` DervishD
2004-05-07 8:57 ` Dick Streefland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=409B3930.9B0C9659@melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=tennert@science-computing.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox