All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: [PATCH] SGI 905314 (2/2): document constraints on client transfer size
Date: Fri, 28 Nov 2003 23:45:52 +1100	[thread overview]
Message-ID: <3FC74380.6367DBAA@melbourne.sgi.com> (raw)

G'day,

SGI bug #905314

This patch adds a comment documenting the actual constraints
on NFS_MAX_FILE_IO_BUFFER_SIZE for the next guy who needs to know ;-)

--- /usr/tmp/TmpDir.28396-0/linux/linux/include/linux/nfs_fs.h_1.21	Fri Nov 28
23:07:47 2003
+++ linux/include/linux/nfs_fs.h	Fri Nov 28 21:55:30 2003
@@ -40,6 +40,18 @@
  */
 #define NFS_MAX_DIRCACHE		16
 
+/* 
+ * NFS_MAX_FILE_IO_BUFFER_SIZE limits the rsize and wsize that
+ * userspace can request in mount options (note that the server
+ * also gives us a limit in response to the FSINFO call).  The
+ * value is constrained by 1) has to fit in a UDP datagram less
+ * some headers 2) has to be a multiple of page size 3) has to
+ * be no more than NFS_READ_MAXIOV=8 pages for rsize, and
+ * NFS_WRITE_MAXIOV=8 pages for wsize and 4) has to be a power
+ * of two (actually this is bogus but nfs_read_super relies on it).
+ * For best performance we usually want the largest value
+ * consistent with these constraints.
+ */
 #define NFS_MAX_FILE_IO_BUFFER_SIZE	32768
 #define NFS_DEF_FILE_IO_BUFFER_SIZE	4096
 



Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2003-11-28 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FC74380.6367DBAA@melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.