linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>,
	<Trond.Myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 00/17] NFS: Create a common path used by reads and writes
Date: Wed, 23 Apr 2014 15:55:03 +0300	[thread overview]
Message-ID: <5357B827.8040506@panasas.com> (raw)
In-Reply-To: <1397768981-12856-1-git-send-email-Anna.Schumaker@Netapp.com>

On 04/18/2014 12:09 AM, Anna Schumaker 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 that don't currently apply.  They need
> 	more testing, and I figured this was enough code churn already.
> 
> 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.
> 
> Questions?  Comments?  Death threats?
> 
> Anna

Good god. Anna did I already tell you that I like you a lot.

This "Identical code but the name" bothered me so much, to no end,
for so long. I envy you that you got to do it finally and so simple
it is.

After you are done there is bunch of code coalescing to do at
pnfs-objects as well. which will be real fun.

Thanks for doing this. Looks very good so far, yes please keep
it on a public tree for quick testing. Perhaps ask Trond to keep
it on his tree in a branch. (So to get some coverage under the linux-next
tree mongers from Intel)

real real cool, spring day
Boaz


  parent reply	other threads:[~2014-04-23 12:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 21:09 [PATCH 00/17] NFS: Create a common path used by reads and writes Anna Schumaker
2014-04-17 21:09 ` [PATCH 01/17] NFS: Create a common argument structure for " Anna Schumaker
2014-04-18 13:56   ` Christoph Hellwig
2014-04-21 12:44     ` Anna Schumaker
2014-04-17 21:09 ` [PATCH 02/17] NFS: Create a common results " Anna Schumaker
2014-04-18 13:57   ` Christoph Hellwig
2014-04-21 12:45     ` Anna Schumaker
2014-04-17 21:09 ` [PATCH 03/17] NFS: Create a common read and write data struct Anna Schumaker
2014-04-18 14:00   ` Christoph Hellwig
2014-04-17 21:09 ` [PATCH 04/17] NFS: Create a common read and write header struct Anna Schumaker
2014-04-18 14:01   ` Christoph Hellwig
2014-04-17 21:09 ` [PATCH 05/17] NFS: Move the write verifier into the nfs_pgio_header Anna Schumaker
2014-04-18 14:02   ` Christoph Hellwig
2014-04-17 21:09 ` [PATCH 06/17] NFS: Create a common pgio_alloc and pgio_release function Anna Schumaker
2014-04-18 14:03   ` Christoph Hellwig
2014-04-17 21:09 ` [PATCH 07/17] NFS: Create a common rw_header_alloc and rw_header_free function Anna Schumaker
2014-04-21 13:32   ` Christoph Hellwig
2014-04-21 13:52     ` Anna Schumaker
2014-04-21 16:24       ` Anna Schumaker
2014-04-25 12:12         ` Christoph Hellwig
2014-04-25 13:02           ` Anna Schumaker
2014-04-17 21:09 ` [PATCH 08/17] NFS: Create a common pgio_rpc_prepare function Anna Schumaker
2014-04-17 21:09 ` [PATCH 09/17] NFS: Create a common nfs_pgio_result_common function Anna Schumaker
2014-04-17 21:09 ` [PATCH 10/17] NFS: Create a common rpc_call_ops struct Anna Schumaker
2014-04-17 21:09 ` [PATCH 11/17] NFS: Create a common rpcsetup function for reads and writes Anna Schumaker
2014-04-17 21:09 ` [PATCH 12/17] NFS: Create a common pgio_error function Anna Schumaker
2014-04-17 21:09 ` [PATCH 13/17] NFS: Create a generic_pgio function Anna Schumaker
2014-04-17 21:09 ` [PATCH 14/17] NFS: Create a common initiate_pgio() function Anna Schumaker
2014-04-17 21:09 ` [PATCH 15/17] NFS: Create a common multiple_pgios() function Anna Schumaker
2014-04-17 21:09 ` [PATCH 16/17] NFS: Create a common generic_pg_pgios() Anna Schumaker
2014-04-17 21:09 ` [PATCH 17/17] NFS: Create a common nfs_pageio_ops struct Anna Schumaker
2014-04-21  6:42 ` [PATCH 00/17] NFS: Create a common path used by reads and writes Christoph Hellwig
2014-04-21 12:46   ` Anna Schumaker
2014-04-21 13:09     ` Christoph Hellwig
2014-04-23 12:55 ` Boaz Harrosh [this message]
2014-04-23 13:15   ` Boaz Harrosh
2014-04-23 13:42     ` Weston Andros Adamson
2014-04-23 13:51       ` Anna Schumaker
2014-04-23 13:59         ` Boaz Harrosh

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=5357B827.8040506@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=Trond.Myklebust@primarydata.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).