mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Tennert <tennert@science-computing.de>
To: neilb@cse.unsw.edu.au
Cc: linux-kernel@vger.kernel.org
Subject: PATCH [NFSd] NFSv3/TCP
Date: Fri, 7 May 2004 08:39:29 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0405070834001.4547-100000@picard.science-computing.de> (raw)

Hi Neil (and others),

is there any reason why current 2.4 kernels do not allow for
NFSSVC_MAXBLKSIZE to become as large as 32k?

The problem is when I use NFSv3/TCP with a 2.4.25, say, on the server
side, as well as on the client side, I am experiencing lockups when
copying medium-sized or large files from the NFS fs to a local fs.

But, after applying the following trivial patch, everything is well again:

--- linux-2.4.26-1/include/linux/nfsd/const.h.ORG       Mon May  3
16:20:18 2004
+++ linux-2.4.26-1/include/linux/nfsd/const.h   Mon May  3 16:20:32 2004
@@ -19,9 +19,9 @@
 #define NFSSVC_MAXVERS         3

 /*
- * Maximum blocksize supported by daemon currently at 8K
+ * Maximum blocksize supported by daemon currently at 32K
  */
-#define NFSSVC_MAXBLKSIZE      (8*1024)
+#define NFSSVC_MAXBLKSIZE      (32*1024)

 #ifdef __KERNEL__

32k is the maximum block size allowed by the NFS3 standard, as far as I
understand.

I realize that, before 2.4.19, this patch was part of the NFSv3/TCP server
patches, before this functionality got into the vanilla kernel. But with
the merge, this patch got lost! Is there any reason?

Best regards

Oliver

__
________________________________________creating IT solutions

Dr. Oliver Tennert			science + computing ag
phone   +49(0)7071 9457-598		Hagellocher Weg 71-75
fax     +49(0)7071 9457-411		D-72070 Tuebingen, Germany
O.Tennert@science-computing.de		www.science-computing.de




             reply	other threads:[~2004-05-07  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  6:39 Oliver Tennert [this message]
2004-05-07  6:47 ` Neil Brown
2004-05-07  7:19   ` Oliver Tennert
2004-05-07  7:22   ` Greg Banks
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=Pine.LNX.4.44.0405070834001.4547-100000@picard.science-computing.de \
    --to=tennert@science-computing.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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

all inboxes | Powered by JetHome®