Linux NFS development
 help / color / mirror / Atom feed
From: James Pearson <james-p-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Support for larger than 32Kb [rw]size in older 2.6 kernels?
Date: Wed, 22 Apr 2009 17:36:39 +0100	[thread overview]
Message-ID: <49EF4797.2070402@moving-picture.com> (raw)

We have a number of machines that use RHEL4 kernels that run 3rd party 
software/hardware that we can't upgrade to run on newer kernels.

I've managed (I think!) to backport the large [rw]size patch that went 
into 2.6.16 to the RHEL4 2.6.9 based kernels - taken from:

<http://www.linux-nfs.org/Linux-2.6.x/2.6.15/linux-2.6.15-30-large_wsize_support.dif>

Doing some simple tests over NFS using this patch seems to suggest that 
it works fine.

Although the NFS code between the two kernel is significantly different, 
  it was fairly straight forward to match up where the changes should go 
-  however, I don't pretend to fully understand the code, so is there 
anything that I should be aware of that might cause a problem? i.e. does 
larger [rw]size depend on anything else that that would have been added 
to the kernel since 2.6.9?

One thing that isn't in the RHEL4 is 'rpc_max_payload' - which is used 
as a check on the [rw]size - however, this appears not to be important 
as the maximum [rw]size I can get is 1Mb, which matches the max [rw]size 
with more recent kernels.

Thanks

James Pearson


                 reply	other threads:[~2009-04-22 17:06 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=49EF4797.2070402@moving-picture.com \
    --to=james-p-5ol4pytxkwu0ml75eksnrtbpr1lh4cv8@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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