From: Anna Schumaker <bjschuma@netapp.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: <bfields@fieldses.org>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] NFSD: Implement SEEK
Date: Thu, 14 Nov 2013 14:17:51 -0500 [thread overview]
Message-ID: <528521DF.5040201@netapp.com> (raw)
In-Reply-To: <CALXu0UfQuj+BNntibGf3CXcBnbP0pHTnZ5-Rp6FAwhfeNxjoow@mail.gmail.com>
On 11/14/2013 11:47 AM, Cedric Blancher wrote:
> On 13 November 2013 20:30, Anna Schumaker <bjschuma@netapp.com> wrote:
>> These patches implement just the SEEK NFS v4.2 operation. WRITE_PLUS is
>> still under discussion with the IETF after my last series of patches, so I
>> am holding off on resubmitting until after spec discussion dies down.
>>
>> Questions? Comments? Thoughts?
>> Anna
>
> 1. Doesn't SEEK_HOLE/SEEK_DATA already work in NFSv4? I always had the
> impression this worked there...
If we did, it was vfs-level seeking. HOLE and DATA support are new to NFS with v4.2.
>
> 2. Does http://svn.nrubsig.org/svn/people/gisburn/code/sparsefiles/lsholes.c
> work with your changes (the name is unfortunate, but its useful to
> list the holes in a file and even has a short test)?
lsholes.c passes on NFS with these changes, although I think it needs a "-h" option to tell me how to use it without looking at the code :)
>
> 3. If you implement SEEK_HOLE/SEEK_DATA support you have to alter
> fpathconf() support and implement the _PC_MIN_HOLE_SIZE properly.
I don't think the NFS server exports a "minimum hole size" attribute, so I don't know how to find this without spec changes.
Anna
>
> Ced
>
prev parent reply other threads:[~2013-11-14 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 19:30 [PATCH v3 0/3] NFSD: Implement SEEK Anna Schumaker
2013-11-13 19:30 ` [PATCH v3 1/3] NFSD: Update error codes Anna Schumaker
2013-11-13 19:30 ` [PATCH v3 2/3] NFSD: Create nfs v4.2 decode ops Anna Schumaker
2013-11-13 19:30 ` [PATCH v3 3/3] NFSD: Implement SEEK Anna Schumaker
2013-11-13 20:01 ` Weston Andros Adamson
2013-11-13 20:02 ` Anna Schumaker
2013-11-14 16:25 ` [PATCH v4 " Anna Schumaker
2013-11-14 16:47 ` [PATCH v3 0/3] " Cedric Blancher
2013-11-14 19:17 ` Anna Schumaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=528521DF.5040201@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=cedric.blancher@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).