NfsRdmaClient/Home
From Linux NFS
Chucklever (Talk | contribs) m (→Submitting patches) |
Chucklever (Talk | contribs) (→Submitting patches) |
||
| Line 41: | Line 41: | ||
General advice for preparing upstream kernel or nfs-utils patches: see [https://www.kernel.org/doc/Documentation/SubmittingPatches SubmittingPatches]. | General advice for preparing upstream kernel or nfs-utils patches: see [https://www.kernel.org/doc/Documentation/SubmittingPatches SubmittingPatches]. | ||
| - | Submit patches to linux-nfs@vger.kernel.org. For RPC/RDMA patches, consider courtesy-copying linux-rdma@vger.kernel.org. | + | 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. Be sure to label your patch "untested" or "for review only" in that case. |
| + | |||
| + | Submit patches to linux-nfs@vger.kernel.org for review. For RPC/RDMA patches, consider courtesy-copying linux-rdma@vger.kernel.org. | ||
=== Engineering Notes === | === Engineering Notes === | ||
* [[NfsRdmaClient/MemRegModes|Simplifying memory registration modes]] | * [[NfsRdmaClient/MemRegModes|Simplifying memory registration modes]] | ||
Revision as of 01:03, 10 April 2014
Contents |
Support for Linux NFS/RDMA Client upstream
Goals
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.
Bug tracking
Upstream bug tracking is here.
Feature planning
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
Developer tools
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
- fsx
- IOzone
- fio
- 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 linux-nfs@vger.kernel.org, or in the linux-nfs chatroom at oftc.net.
Submitting patches
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. Be sure to label your patch "untested" or "for review only" in that case.
Submit patches to linux-nfs@vger.kernel.org for review. For RPC/RDMA patches, consider courtesy-copying linux-rdma@vger.kernel.org.
