From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Weston Andros Adamson <dros@primarydata.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3 00/17] NFS: Create a common path used by reads and writes
Date: Wed, 28 May 2014 19:02:14 -0400 [thread overview]
Message-ID: <CAHQdGtTEceDpfjnUMotTgqkwMoTQaRYgSwWGLXudTsg0U+opDA@mail.gmail.com> (raw)
In-Reply-To: <1399381960-3019-1-git-send-email-Anna.Schumaker@Netapp.com>
On Tue, May 6, 2014 at 9:12 AM, Anna Schumaker
<Anna.Schumaker@netapp.com> wrote:
> I noticed that much of the read and write code was almost identical, with
> only minor differences in argument types and names. These patches seek to
> unify these two codepaths wherever possible in order to make future changes
> easier.
>
> Table of contents:
> Patches 01 - 05: Set up common data structures.
> Patches 06 - 10: Set up a shared rpc_call_ops struct.
> Patches 11 - 15: Set up a shared nfs_pageio_ops struct.
>
> Some of the commit setup was moved into common code, but I'm willing to
> move this back into write.c if this looks to be a problem.
>
> Future work:
> I have rough pNFS patches to combine the read and write paths in
> pnfs.c. They apply on top of Dros' multiple requests work and
> should get more testing before I submit.
>
> Testing:
> I tested every version of NFS using the cthon and xfs tests without
> hitting anything new. Any extra testing would be great seeing how
> the read and write paths are vitally important.
>
> Changes in v3:
> Instead of creating a new "pageio.c" file, I now put the combined
> code into pagelist.c (good luck, Dros!)
>
> I also renamed a few functions, and did a better job checking what
> pagelist.c functions can now be static.
>
> Questions? Comments? Thoughts?
>
Thanks for working on this! Applied...
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
prev parent reply other threads:[~2014-05-28 23:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 13:12 [PATCH v3 00/17] NFS: Create a common path used by reads and writes Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 01/17] NFS: Create a common argument structure for " Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 02/17] NFS: Create a common results " Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 03/17] NFS: Create a common read and write data struct Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 04/17] NFS: Create a common read and write header struct Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 05/17] NFS: Move the write verifier into the nfs_pgio_header Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 06/17] NFS: Create a common pgio_alloc and pgio_release function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 07/17] NFS: Create a common rw_header_alloc and rw_header_free function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 08/17] NFS: Create a common pgio_rpc_prepare function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 09/17] NFS: Create a common nfs_pgio_result_common function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 10/17] NFS: Create a common rpc_call_ops struct Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 11/17] NFS: Create a common rpcsetup function for reads and writes Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 12/17] NFS: Create a common pgio_error function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 13/17] NFS: Create a generic_pgio function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 14/17] NFS: Create a common initiate_pgio() function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 15/17] NFS: Create a common multiple_pgios() function Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 16/17] NFS: Create a common generic_pg_pgios() Anna Schumaker
2014-05-06 13:12 ` [PATCH v3 17/17] NFS: Create a common nfs_pageio_ops struct Anna Schumaker
2014-05-06 13:28 ` [PATCH v3 00/17] NFS: Create a common path used by reads and writes Weston Andros Adamson
2014-05-13 15:21 ` Weston Andros Adamson
2014-05-28 23:02 ` Trond Myklebust [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=CAHQdGtTEceDpfjnUMotTgqkwMoTQaRYgSwWGLXudTsg0U+opDA@mail.gmail.com \
--to=trond.myklebust@primarydata.com \
--cc=Anna.Schumaker@netapp.com \
--cc=dros@primarydata.com \
--cc=hch@infradead.org \
--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).