From: Dave Wysochanski <dwysocha@redhat.com>
To: Anna Schumaker <anna.schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: linux-nfs@vger.kernel.org, linux-cachefs@redhat.com,
David Howells <dhowells@redhat.com>
Subject: [PATCH 0/4] Cleanups for NFS fscache and convert from dfprintk to trace events
Date: Tue, 1 Mar 2022 14:37:23 -0500 [thread overview]
Message-ID: <20220301193727.18847-1-dwysocha@redhat.com> (raw)
This is a re-post of these patches, unchanged from previous postings [1][2],
rebased on top of 5.17-rc5.
The patches were dependent on dhowells patchset which was taken in the
last merge window, so they apply on 5.17-rc5 cleanly now.
[1] https://marc.info/?l=linux-nfs&m=164225455702418&w=2
[2] https://marc.info/?l=linux-nfs&m=163976362831065&w=2
Dave Wysochanski (4):
NFS: Cleanup usage of nfs_inode in fscache interface
NFS: Rename fscache read and write pages functions
NFS: Replace dfprintks with tracepoints in fscache read and write page functions
NFS: Remove remaining dfprintks related to fscache and remove NFSDBG_FSCACHE
fs/nfs/fscache.c | 53 +++++++--------------
fs/nfs/fscache.h | 45 ++++++++----------
fs/nfs/nfstrace.h | 91 +++++++++++++++++++++++++++++++++++++
fs/nfs/read.c | 4 +-
include/uapi/linux/nfs_fs.h | 2 +-
5 files changed, 130 insertions(+), 65 deletions(-)
--
2.27.1
next reply other threads:[~2022-03-01 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 19:37 Dave Wysochanski [this message]
2022-03-01 19:37 ` [PATCH 1/4] NFS: Cleanup usage of nfs_inode in fscache interface Dave Wysochanski
2022-03-01 19:37 ` [PATCH 2/4] NFS: Rename fscache read and write pages functions Dave Wysochanski
2022-03-01 19:37 ` [PATCH 3/4] NFS: Replace dfprintks with tracepoints in fscache read and write page functions Dave Wysochanski
2022-03-01 19:37 ` [PATCH 4/4] NFS: Remove remaining dfprintks related to fscache and remove NFSDBG_FSCACHE Dave Wysochanski
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=20220301193727.18847-1-dwysocha@redhat.com \
--to=dwysocha@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--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 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.