From: cel@kernel.org
To: <linux-nfs@vger.kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v3 0/4] Patches for pNFS SCSI layout PR key registration
Date: Tue, 25 Jun 2024 16:02:05 -0400 [thread overview]
Message-ID: <20240625200204.276770-5-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
I've dropped the alloc_bulk_pages_array() patch, as it seemed
slightly less reliable than allocating a page at a time on my
small-memory test system.
I do not currently have a set up that can test slice/concat
configurations, but the simple/scsi volume type is stable (except
for generic/450).
---
Changes since v2:
- Support more complex volume types
- Dropped the alloc_bulk_pages_array() patch
Changes since RFC:
- series re-ordered to place fixes first
- address review comments as best I can
Chuck Lever (3):
nfs/blocklayout: Fix premature PR key unregistration
nfs/blocklayout: Report only when /no/ device is found
nfs/blocklayout: SCSI layout trace points for reservation key
reg/unreg
fs/nfs/blocklayout/blocklayout.c | 25 ++++---
fs/nfs/blocklayout/blocklayout.h | 9 ++-
fs/nfs/blocklayout/dev.c | 116 +++++++++++++++++++++++--------
fs/nfs/nfs4trace.c | 7 ++
fs/nfs/nfs4trace.h | 88 +++++++++++++++++++++++
5 files changed, 205 insertions(+), 40 deletions(-)
--
2.45.1
next reply other threads:[~2024-06-25 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 20:02 cel [this message]
2024-06-25 20:02 ` [PATCH v3 1/3] nfs/blocklayout: Fix premature PR key unregistration cel
2024-06-26 5:19 ` Christoph Hellwig
2024-06-26 13:43 ` Chuck Lever III
2024-06-26 14:49 ` Benjamin Coddington
2024-06-26 14:52 ` Chuck Lever
2024-06-25 20:02 ` [PATCH v3 2/3] nfs/blocklayout: Report only when /no/ device is found cel
2024-06-25 20:02 ` [PATCH v3 3/3] nfs/blocklayout: SCSI layout trace points for reservation key reg/unreg cel
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=20240625200204.276770-5-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.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.