From Linux NFS
Support for Linux NFS/RDMA Client upstream
Provide maintenance for NFS/RDMA and RPC/RDMA client-side code in the Linux kernel. Support continuous testing of NFS/RDMA feature in upstream Linux kernels. Provide enhancements (see below). Identify resources for supporting server-side code.
Upstream bug tracking is here.
Our Pivotal Tracking project lists individual work items and defines several long-term arcs. At a high level, these include:
- Broad support for a variety of RDMA-capable hardware
- Performance and scalability enhancements
- Support for NFSv4.1
- Observability features that enable distributor support teams and customers to diagnose and address problems
For anyone working directly on Linux NFS/RDMA or RPC/RDMA, please consider the following tools for validating your work.
- cthon04: git://git.linux-nfs.org/projects/steved/cthon04.git
- xfstests: git://oss.sgi.com/xfs/cmds/xfstests
- nfs-o-meter: git://git.linux-nfs.org/projects/dros/nfsometer.git
- Multi-process Linux kernel builds
Typically, for testing, the NFS/RDMA server exports a tmpfs or ram disk-based local FS to drive the transport fast enough.
Asking for help
You can find Linux NFS developers at email@example.com, or in the linux-nfs chatroom at oftc.net.
Clone the upstream Linux kernel with:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
General advice for preparing upstream kernel or nfs-utils patches: see SubmittingPatches.
It is strongly recommended that patches be compile-tested, tested with sparse, and run by scripts/checkpatch.pl before submission. Patches should be tested with the tools above before submission, though that's not needed if you are posting only for review.
Review is done via e-mail. In the kernel source tree, see Documentation/email-clients.txt for important advice on how to use e-mail to submit patches.
Label your patches "[RFC ... ]" or "untested" "DO NOT APPLY" or "for review only" so maintainers know the patch is for review and may not be broadly tested yet.
Submit patches to firstname.lastname@example.org and email@example.com for review.
If you have reviewed a posted patch, reply with a "Reviewed-by:". If you've tested it, reply with a "Tested-by:"
When the community feels a client-side patch is ready to be merged, submit the patches again (without "for review" disclaimers) to firstname.lastname@example.org and email@example.com, and cc: Anna.Schumaker@netapp.com. Anna will collect ready patches for Trond to merge upstream.
We are still developing a mechanism for requesting server-side fixes be merged.