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
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
