From: Jeff Layton <jeffrey.b.layton@lmco.com>
To: nfs@lists.sourceforge.net
Subject: Changing block size in 2.4.20 kernel
Date: Tue, 22 Jul 2003 12:04:57 -0400 [thread overview]
Message-ID: <3F1D60A9.1010203@lmco.com> (raw)
Hello,
I'd like to increase the block size in the 2.4.20 kernel (can't upgrade
for various reasons) and I can't apply the TCP patches that change it.
This particular machine is a server for a beowulf, so it's a Linux
server for Linux clients (all the same kernel).
If I change ./include/linux/nfsd/const.h, NFSSVC_MAXBLKSIZE
to 32k (32768), rebuild, reinstall, reboot, etc. Will this then change
the blocksize for the NFS server? (I just want to be sure :) Then the
clients can handle a 32k blocksize even running UDP? (Again, I
just want to be sure :)
TIA!
Jeff
--
Dr. Jeff Layton
Chart Monkey - Aerodynamics and CFD
Lockheed-Martin Aeronautical Company - Marietta
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2003-07-22 16:50 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=3F1D60A9.1010203@lmco.com \
--to=jeffrey.b.layton@lmco.com \
--cc=nfs@lists.sourceforge.net \
/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