linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Jeff Layton <jlayton@redhat.com>, <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>, <tigran.mkrtchyan@desy.de>
Subject: Re: [PATCH v4 resend 0/2] pnfs: allow client to support servers that send multiple layout types
Date: Mon, 19 Sep 2016 13:13:42 -0400	[thread overview]
Message-ID: <abcb0fdd-b2da-0208-c57a-66c2c5ce83b9@Netapp.com> (raw)
In-Reply-To: <1473964849-3194-1-git-send-email-jlayton@redhat.com>

On 09/15/2016 02:40 PM, Jeff Layton wrote:
> Resending as I noticed that Anna had merged the first of the two
> patches into her linux-next branch, but not the second one. Were
> there any further concerns with it?

Nope, no concerns.  I updated a few of the later patchsets in my branch before pushing everything out, so it must have gotten lost in the shuffle.  I've applied the patch again, so it should be there now.  Thanks for catching!

Sorry about the mistake, and thanks for catching it!
Anna

> 
> v4:
> - pass around fsinfo instead of separate array and length args
> 
> v3:
> - use sort() from lib/sort.c to sort the list
> 
> v2:
> - rework Tigran's patch to preserve existing selection behaviour
> - simplify layout driver selection by sorting the list
> 
> This is v4 of the patchset. The main change is the change to pass
> around the fsinfo instead of separate array pointer and length args.
> 
> Only lightly tested by mounting a server that sends both flexfiles and
> block layouts. The client successfully selected the block layout in most
> cases, but if I blacklist blocklayoutdriver then it selects flexfiles
> instead.
> 
> Jeff Layton (2):
>   pnfs: track multiple layout types in fsinfo structure
>   pnfs: add a new mechanism to select a layout driver according to an
>     ordered list
> 
>  fs/nfs/client.c         |  3 ++-
>  fs/nfs/nfs4proc.c       |  2 +-
>  fs/nfs/nfs4xdr.c        | 40 ++++++++++++++--------------
>  fs/nfs/pnfs.c           | 69 ++++++++++++++++++++++++++++++++++++++++---------
>  fs/nfs/pnfs.h           |  5 ++--
>  include/linux/nfs_xdr.h |  8 +++++-
>  6 files changed, 91 insertions(+), 36 deletions(-)
> 


      parent reply	other threads:[~2016-09-19 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 18:40 [PATCH v4 resend 0/2] pnfs: allow client to support servers that send multiple layout types Jeff Layton
2016-09-15 18:40 ` [PATCH v4 resend 1/2] pnfs: track multiple layout types in fsinfo structure Jeff Layton
2016-09-15 18:40 ` [PATCH v4 resend 2/2] pnfs: add a new mechanism to select a layout driver according to an ordered list Jeff Layton
2016-09-19 17:13 ` 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=abcb0fdd-b2da-0208-c57a-66c2c5ce83b9@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    --cc=trond.myklebust@primarydata.com \
    /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).