All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Tao <bergwolf@primarydata.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 4/4] pnfs: remove GETDEVICELIST implementation
Date: Thu, 11 Sep 2014 22:51:17 +0800	[thread overview]
Message-ID: <CAKVebiWqxFF8GO4kkVr7AtO0gTC+o1Zb0QpfU4wC_oSAoeG-AQ@mail.gmail.com> (raw)
In-Reply-To: <1410395791-2385-5-git-send-email-hch@lst.de>

On Thu, Sep 11, 2014 at 8:36 AM, Christoph Hellwig <hch@lst.de> wrote:
> The current GETDEVICELIST implementation is buggy in that it doesn't handle
> cursors correctly, and in that it returns an error if the server returns
> NFSERR_NOTSUPP.  Given that there is no actual need for GETDEVICELIST,
> it has various issues and might get removed for NFSv4.2 stop using it in
> the blocklayout driver, and thus the Linux NFS client as whole.
>
I am missing patch 3/4, which I assume would fill in the gap where
GETDEVICEINFO is sent for block layout. Can you please resent that?

Cheers,
Tao

  reply	other threads:[~2014-09-11 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  0:36 a few more pnfs/blocklayout fixes Christoph Hellwig
2014-09-11  0:36 ` [PATCH 1/4] pnfs/blocklayout: remove some debugging Christoph Hellwig
2014-09-11  0:36 ` [PATCH 2/4] pnfs/objlayout: fix endianess annotation in objio_alloc_deviceid_node Christoph Hellwig
2014-09-11  0:36 ` [PATCH 3/4] pnfs/blocklayout: allocate separate pages for the layoutcommit payload Christoph Hellwig
2014-09-11 14:16   ` Anna Schumaker
2014-09-11 15:27     ` Christoph Hellwig
2014-09-11 15:59       ` Anna Schumaker
2014-09-11 16:00       ` Anna Schumaker
2014-09-11  0:36 ` [PATCH 4/4] pnfs: remove GETDEVICELIST implementation Christoph Hellwig
2014-09-11 14:51   ` Peng Tao [this message]
2014-09-11 15:29     ` Christoph Hellwig

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=CAKVebiWqxFF8GO4kkVr7AtO0gTC+o1Zb0QpfU4wC_oSAoeG-AQ@mail.gmail.com \
    --to=bergwolf@primarydata.com \
    --cc=hch@lst.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.