cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCHv2 dlm/next 0/3] fs: dlm: tracepoint changes
Date: Wed,  1 Jun 2022 18:44:51 -0400	[thread overview]
Message-ID: <20220601224454.1640688-1-aahringo@redhat.com> (raw)

Hi,

this patch series contains some changes to the dlm tracepoint system.
Now we can ask about if stable candidate or not, the dlm tracepoint
system is relative new and I am doing some experiments right now and
need those changes. It should be still backward compatible... may some
small changes e.g. calling bast/ast tracepoint before calling callback
which makes more sense as other way around... I think it's fine to put
them in next as they are development tools anyway.

- Alex

changes since v2:
 - remove the not working +1 terminated null in res_name field to
   provide a null terminated string, the user need to deal with it now.

Alexander Aring (3):
  fs: change ast and bast trace order
  fs: remove additional dereference of lkbsb
  fs: dlm: add resource name to tracepoints

 fs/dlm/ast.c               |   4 +-
 fs/dlm/lock.c              |   4 +-
 include/trace/events/dlm.h | 118 ++++++++++++++++++++++++++++++-------
 3 files changed, 100 insertions(+), 26 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-06-01 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 22:44 Alexander Aring [this message]
2022-06-01 22:44 ` [Cluster-devel] [PATCHv2 dlm/next 1/3] fs: change ast and bast trace order Alexander Aring
2022-06-01 22:44 ` [Cluster-devel] [PATCHv2 dlm/next 2/3] fs: remove additional dereference of lkbsb Alexander Aring
2022-06-01 22:44 ` [Cluster-devel] [PATCHv2 dlm/next 3/3] fs: dlm: add resource name to tracepoints Alexander Aring

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=20220601224454.1640688-1-aahringo@redhat.com \
    --to=aahringo@redhat.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).