On Thu, 2012-04-05 at 19:03 -0500, Calvin Owens wrote: > Hello all, > > I'm interested in implementing the draft specification for NFS v4.2 as a > Google Summer of Code project. That includes server-side copying, sparse > files, and carrying fadvise() calls through to the server, among other > things. > > The current document can be found here: > http://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-07 > > Is this something that you need to be done? If so, I'd very much like to > be involved. :) Hi Calvin, Labelled NFS is likely to be merged into 3.5 (if Dave Q finds the time to port his existing code). Copy offload already exists in prototype form. The main remaining issue is working out the user syscall interface, which really requires getting all the interested filesystem maintainers to agree (we've started on doing that). If you'd like to contribute, then I'd suggest looking into SEEK (for providing lseek(SEEK_HOLE/SEEK_DATA) support. There is also the hole punching/space reservation, that should fit nicely into the fallocate() system call. The efficient sparse file read and fadvise support might be nice too, but I'd like to see numbers for how they improve matters before I feel comfortable saying yea or nay to adding those specific features. Note that there are also a bunch of NFSv4.1 features that have yet to be implemented, so the above list of tasks is not exhaustive. I'd be happy to work with you to find something... Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com ��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
