From: Sergey Bashirov <sergeybashirov@gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Evtushenko <koevtushenko@yandex.com>,
Sergey Bashirov <sergeybashirov@gmail.com>
Subject: [PATCH v4 0/2] nfsd: Implement large extent array support in pNFS
Date: Sat, 21 Jun 2025 19:52:43 +0300 [thread overview]
Message-ID: <20250621165409.147744-1-sergeybashirov@gmail.com> (raw)
This series is the result of splitting the patch v3. Removing dprintk is
now done in a separate cleanup commit. No additional changes.
Prerequisite patch: [v3] nfsd: Use correct error code when decoding extents
Signed-off-by: Sergey Bashirov <sergeybashirov@gmail.com>
---
Sergey Bashirov (2):
nfsd: Drop dprintk in blocklayout xdr functions
nfsd: Implement large extent array support in pNFS
fs/nfsd/blocklayout.c | 20 ++++---
fs/nfsd/blocklayoutxdr.c | 118 ++++++++++++++++++++-------------------
fs/nfsd/blocklayoutxdr.h | 4 +-
fs/nfsd/nfs4proc.c | 2 +-
fs/nfsd/nfs4xdr.c | 11 ++--
fs/nfsd/pnfs.h | 1 +
fs/nfsd/xdr4.h | 3 +-
7 files changed, 83 insertions(+), 76 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-21 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 16:52 Sergey Bashirov [this message]
2025-06-21 16:52 ` [PATCH v4 1/2] nfsd: Drop dprintk in blocklayout xdr functions Sergey Bashirov
2025-06-21 18:46 ` Jeff Layton
2025-06-23 7:34 ` Christoph Hellwig
2025-06-21 16:52 ` [PATCH v4 2/2] nfsd: Implement large extent array support in pNFS Sergey Bashirov
2025-06-21 19:08 ` Jeff Layton
2025-06-23 7:41 ` Christoph Hellwig
2025-06-23 13:50 ` [PATCH v4 0/2] " Chuck Lever
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=20250621165409.147744-1-sergeybashirov@gmail.com \
--to=sergeybashirov@gmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=koevtushenko@yandex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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).