From: Andreas Gruenbacher <agruenba@redhat.com>
To: gfs2@lists.linux.dev
Cc: Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH 00/15] gfs2: Revise glock refcounting
Date: Wed, 29 May 2024 19:03:37 +0200 [thread overview]
Message-ID: <20240529170352.571141-1-agruenba@redhat.com> (raw)
Here is a patch queue for the next (6.11) merge window. After a number
of cleanups, the glock reference counting model is modified so that the
number of references no longer depends on whether or not the glock is
locked. This allows to eliminate the go_demote_ok() glock operation.
Thanks,
Andreas
Andreas Gruenbacher (15):
gfs2: Remove unnecessary function prototype
gfs2: Remove useless return statement in run_queue
gfs2: Rename GLF_FREEING to GLF_UNLOCKED
gfs2: Rename GLF_REPLY_PENDING to GLF_HAVE_REPLY
gfs2: Rename GLF_FROZEN to GLF_HAVE_FROZEN_REPLY
gfs2: Rename handle_callback to request_demote
gfs2: Update glocks documentation
gfs2: Remove outdated comment in glock_work_func
gfs2: Invert the GLF_INITIAL flag
gfs2: gfs2_glock_get cleanup
gfs2: Report when glocks cannot be freed for a long time
gfs2: Switch to a per-filesystem glock workqueue
gfs2: Revise glock reference counting model
Revert "GFS2: Don't add all glocks to the lru"
gfs2: Get rid of demote_ok checks
Documentation/filesystems/gfs2-glocks.rst | 55 +++---
fs/gfs2/glock.c | 215 ++++++++++------------
fs/gfs2/glock.h | 1 -
fs/gfs2/glops.c | 42 ++---
fs/gfs2/incore.h | 11 +-
fs/gfs2/lock_dlm.c | 28 ++-
fs/gfs2/ops_fstype.c | 12 +-
fs/gfs2/super.c | 1 -
fs/gfs2/trace_gfs2.h | 6 +-
fs/gfs2/util.c | 6 +-
10 files changed, 171 insertions(+), 206 deletions(-)
--
2.45.1
next reply other threads:[~2024-05-29 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 17:03 Andreas Gruenbacher [this message]
2024-05-29 17:03 ` [PATCH 01/15] gfs2: Remove unnecessary function prototype Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 02/15] gfs2: Remove useless return statement in run_queue Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 03/15] gfs2: Rename GLF_FREEING to GLF_UNLOCKED Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 04/15] gfs2: Rename GLF_REPLY_PENDING to GLF_HAVE_REPLY Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 05/15] gfs2: Rename GLF_FROZEN to GLF_HAVE_FROZEN_REPLY Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 06/15] gfs2: Rename handle_callback to request_demote Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 07/15] gfs2: Update glocks documentation Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 08/15] gfs2: Remove outdated comment in glock_work_func Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 09/15] gfs2: Invert the GLF_INITIAL flag Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 10/15] gfs2: gfs2_glock_get cleanup Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 11/15] gfs2: Report when glocks cannot be freed for a long time Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 12/15] gfs2: Switch to a per-filesystem glock workqueue Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 13/15] gfs2: Revise glock reference counting model Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 14/15] Revert "GFS2: Don't add all glocks to the lru" Andreas Gruenbacher
2024-05-29 17:03 ` [PATCH 15/15] gfs2: Get rid of demote_ok checks Andreas Gruenbacher
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=20240529170352.571141-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).