Linux NFS development
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com
Cc: anna@kernel.org
Subject: [PATCH v1 0/9] SUNRPC: Convert the scratch page into a scratch folio
Date: Fri, 12 Sep 2025 17:14:00 -0400	[thread overview]
Message-ID: <20250912211410.837006-1-anna@kernel.org> (raw)

From: Anna Schumaker <anna.schumaker@oracle.com>

This is the first of a handful of patchsets I've been working on to
convert our usage of 'struct page's into 'struct folio's. I figured I
would start things off easy with converting the scratch page set to the
xdr_buf before I dive into converting over the page array.

What do you all think?
Anna


Anna Schumaker (9):
  SUNRPC: Introduce xdr_set_scratch_folio()
  NFS: Update readdir to use a scratch folio
  NFS: Update getacl to use xdr_set_scratch_folio()
  NFS: Update listxattr to use xdr_set_scratch_folio()
  NFS: Update the blocklayout to use xdr_set_scratch_folio()
  NFS: Update the filelayout to use xdr_set_scratch_folio()
  NFS: Update the flexfilelayout driver to use xdr_set_scratch_folio()
  SUNRPC: Update svcxdr_init_decode() to call xdr_set_scratch_folio()
  SUNRPC: Update gssx_accept_sec_context() to use
    xdr_set_scratch_folio()

 fs/nfs/blocklayout/blocklayout.c          |  8 ++++----
 fs/nfs/blocklayout/dev.c                  |  8 ++++----
 fs/nfs/dir.c                              |  8 ++++----
 fs/nfs/filelayout/filelayout.c            | 10 +++++-----
 fs/nfs/filelayout/filelayoutdev.c         | 10 +++++-----
 fs/nfs/flexfilelayout/flexfilelayout.c    |  8 ++++----
 fs/nfs/flexfilelayout/flexfilelayoutdev.c | 10 +++++-----
 fs/nfs/nfs42proc.c                        |  4 ++--
 fs/nfs/nfs42xdr.c                         |  2 +-
 fs/nfs/nfs4proc.c                         |  4 ++--
 fs/nfs/nfs4xdr.c                          |  2 +-
 include/linux/nfs_xdr.h                   |  4 ++--
 include/linux/sunrpc/svc.h                |  4 ++--
 include/linux/sunrpc/xdr.h                |  8 ++++----
 net/sunrpc/auth_gss/gss_rpc_xdr.c         |  8 ++++----
 net/sunrpc/svc.c                          | 10 +++++-----
 16 files changed, 54 insertions(+), 54 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-09-12 21:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 21:14 Anna Schumaker [this message]
2025-09-12 21:14 ` [PATCH v1 1/9] sunrpc: Introduce xdr_set_scratch_folio() Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 1/9] SUNRPC: " Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 2/9] NFS: Update readdir to use a scratch folio Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 3/9] NFS: Update getacl to use xdr_set_scratch_folio() Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 4/9] NFS: Update listxattr " Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 5/9] NFS: Update the blocklayout " Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 6/9] NFS: Update the filelayout " Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 7/9] NFS: Update the flexfilelayout driver " Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 8/9] SUNRPC: Update svcxdr_init_decode() to call xdr_set_scratch_folio() Anna Schumaker
2025-09-12 21:14 ` [PATCH v1 9/9] SUNRPC: Update gssx_accept_sec_context() to use xdr_set_scratch_folio() Anna Schumaker

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=20250912211410.837006-1-anna@kernel.org \
    --to=anna@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.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