From: Alexander Aring <aahringo@redhat.com>
To: teigland@redhat.com
Cc: gfs2@lists.linux.dev, song@kernel.org, yukuai3@huawei.com,
linux-raid@vger.kernel.org, aahringo@redhat.com
Subject: [PATCH dlm/next 0/8] dlm: md: introduce DLM_LSFL_SOFTIRQ_SAFE
Date: Mon, 3 Jun 2024 17:55:50 -0400 [thread overview]
Message-ID: <20240603215558.2722969-1-aahringo@redhat.com> (raw)
Hi,
the first three patches are resend with an updated commit message and
additional comment e.g. to explain the rcu_read_lock() handling to
avoid a lookup twice.
The main part are the rest of the patches introducing the
DLM_LSFL_SOFTIRQ_SAFE flag to signal that ast/bast callbacks can be
handled in softirq context. md-cluster is the first user here to take
advantage about this flag as their callback handling is simple enough
and looks okay to be called from softirq context. To be honest, I also
just need a upstream user for the new flag. Other users, e.g. gfs2 can
take also advantage of it.
I also gave it a try with a debug kernel and used md-cluster with 2 block
devices and level mirrored. I used gfs2 on top of it and it seems to run
without any problems.
This patch series is based on:
https://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git/log/?h=next
in case of md-cluster people want to try it out.
Thanks.
- Alex
Alexander Aring (8):
dlm: using rcu to avoid rsb lookup again
dlm: remove struct field with the same meaning
dlm: use is_master() on checks if we are the master
dlm: use LSFL_FS to check if it's a kernel lockspace
dlm: introduce DLM_LSFL_SOFTIRQ_SAFE
dlm: implement LSFL_SOFTIRQ_SAFE
dlm: convert ls_cb_lock to rwlock
md-cluster: use DLM_LSFL_SOFTIRQ for dlm_new_lockspace()
drivers/md/md-cluster.c | 2 +-
fs/dlm/ast.c | 185 ++++++++++++++++++---------
fs/dlm/ast.h | 11 +-
fs/dlm/debug_fs.c | 33 ++---
fs/dlm/dlm_internal.h | 40 +++++-
fs/dlm/lock.c | 268 +++++++++++++++++++++++----------------
fs/dlm/lock.h | 5 +-
fs/dlm/lockspace.c | 23 ++--
fs/dlm/memory.c | 15 ++-
fs/dlm/rcom.c | 4 +-
fs/dlm/recover.c | 20 +--
fs/dlm/recoverd.c | 2 +-
fs/dlm/user.c | 38 +++---
include/linux/dlm.h | 17 ++-
include/uapi/linux/dlm.h | 2 +
15 files changed, 413 insertions(+), 252 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-03 21:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 21:55 Alexander Aring [this message]
2024-06-03 21:55 ` [PATCH dlm/next 1/8] dlm: using rcu to avoid rsb lookup again Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 2/8] dlm: remove struct field with the same meaning Alexander Aring
2024-06-10 14:17 ` Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 3/8] dlm: use is_master() on checks if we are the master Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 4/8] dlm: use LSFL_FS to check if it's a kernel lockspace Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 5/8] dlm: introduce DLM_LSFL_SOFTIRQ_SAFE Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 6/8] dlm: implement LSFL_SOFTIRQ_SAFE Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 7/8] dlm: convert ls_cb_lock to rwlock Alexander Aring
2024-06-03 21:55 ` [PATCH dlm/next 8/8] md-cluster: use DLM_LSFL_SOFTIRQ for dlm_new_lockspace() Alexander Aring
2024-06-05 18:54 ` Alexander Aring
2024-06-06 2:48 ` Heming Zhao
2024-06-06 14:33 ` Alexander Aring
2024-06-06 22:55 ` Heming Zhao
2024-06-08 4:21 ` Song Liu
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=20240603215558.2722969-1-aahringo@redhat.com \
--to=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=teigland@redhat.com \
--cc=yukuai3@huawei.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 read-only IMAP folder(s) and NNTP newsgroup(s).