» tagged pages
» logout
v9fs
Return to v9fs

Development Guidelines

(or Cancel)

(Editing anonymously: to be credited for your changes, login or register a new account)

other page actions:

Tags Applied to this Topic

1 person has tagged this page:

Repository and Branches

I’ve created a new git repository (/pub/scm/linux/kernel/git/ericvh/v9fs.git) to eventually replace v9fs-devel.git. This tree will be organized a bit differently with most stuff stored in the following branches:
  • master: will have a pristine linus tree.
  • mm: will have the most recent andrew morton release.
  • v9fs-devel: will be my development tree (which gets pulled into mm)
  • for-linus: will be patches for linus to pull during merge windows

Regression Testing

Right now we request folks perform a sanity check on any changes by running the following benchmarks (available from v9fs CVS on sf.net under the test module):

mount -t 9P 127.0.0.1 /mnt/9
cd /mnt/9/var/tmp
fsx -N 100 -W -d testfile
Bonnie -s 1
echo run | postmark 
ls -l
cd /
umount /mnt/9

A more complicated regression suite is being developed and it will be distributed (along with scripts which run it) shortly. We also request that folks run their builds with Sparse (C=1) to make sure the build is really clean.

Patch Acceptance/Test Process

Please generate patch files with git (git-format-patch-script) and inline email them to v9fs-developer. These patches will go in my patch queue and eventually be merged first into the test branch for baseline regression. Patches passing baseline regression will be merged into the release branch for more thorough testing by the v9fs community, and then be sent as patches to LKML.

Code Style

Follow the Linux kernel guidelines found in Documentation/CodingStyle.

Username:
Password:
(or Cancel)