From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anna.Schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/2] NFSD: Add v4.2 SEEK support
Date: Mon, 22 Sep 2014 13:53:33 -0400 [thread overview]
Message-ID: <20140922175333.GD16658@fieldses.org> (raw)
In-Reply-To: <20140902191043.GD31793@fieldses.org>
On Tue, Sep 02, 2014 at 03:10:43PM -0400, J. Bruce Fields wrote:
> On Tue, Sep 02, 2014 at 01:30:36PM -0400, Anna.Schumaker@netapp.com wrote:
> > From: Anna Schumaker <Anna.Schumaker@Netapp.com>
> >
> > These patches add server support for the NFS v4.2 operation SEEK. The first
> > patch adds basic NFS v4.2 infrastructure that all future operations will rely
> > on. The second patch adds the SEEK operation.
> >
> > Changes in v2:
> > - Remove CONFIG_NFSD_V4_2_SEEK.
> > - Change the call to preprocess_stateid_op() to only use RD_STATE instead of
> > RD_STATE | WR_STATE.
> >
> > These patches and the corresponding client patch are avaliable in the [seek]
> > branch of:
> >
> > git://git.linux-nfs.org/projects/anna/linux-nfs.git
> >
> >
> > Questions? Comments? Thoughts?
>
> They look OK to me. I'll probably merge them once there's evidence
> they're likely to be merged on the client side too.
>
> Also: has anyone done wireshark support for this yet?
Are you sending a new version of these?
(And ditto for the allocate patches.)
As far as I can tell review comments were mostly nits.
--b.
prev parent reply other threads:[~2014-09-22 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 17:30 [PATCH v2 0/2] NFSD: Add v4.2 SEEK support Anna.Schumaker
2014-09-02 17:30 ` [PATCH v2 1/2] NFSD: Add generic v4.2 infrastructure Anna.Schumaker
2014-09-09 17:53 ` Christoph Hellwig
2014-09-02 17:30 ` [PATCH v2 2/2] NFSD: Implement SEEK Anna.Schumaker
2014-09-09 17:56 ` Christoph Hellwig
2014-09-09 19:17 ` Anna Schumaker
2014-09-02 19:10 ` [PATCH v2 0/2] NFSD: Add v4.2 SEEK support J. Bruce Fields
2014-09-22 17:53 ` J. Bruce Fields [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=20140922175333.GD16658@fieldses.org \
--to=bfields@fieldses.org \
--cc=Anna.Schumaker@netapp.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).