From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org
Cc: aron.silverton@oracle.com
Subject: [PATCH RFC 0/3] IB CM tracepoints
Date: Fri, 10 Jul 2020 10:06:01 -0400 [thread overview]
Message-ID: <20200710135812.14749.4630.stgit@klimt.1015granger.net> (raw)
Hi-
This is a Request For Comments.
Oracle has an interest in a common observability infrastructure in
the RDMA core and ULPs. One alternative for this infrastructure is
to introduce static tracepoints that can also be used as hooks for
eBPF scripts, replacing infrastructure that is based on printk.
As an addendum to tracepoints already in NFS/RDMA and parts of the
RDMA core, this series takes that approach as a strawman. Feedback
is welcome!
---
Chuck Lever (3):
RDMA/core: Move the rdma_show_ib_cm_event() macro
RDMA/cm: Replace pr_debug() call sites with tracepoints
RDMA/cm: Add tracepoints to track MAD send operations
drivers/infiniband/core/Makefile | 2 +-
drivers/infiniband/core/cm.c | 102 ++++---
drivers/infiniband/core/cm_trace.c | 15 ++
drivers/infiniband/core/cm_trace.h | 414 +++++++++++++++++++++++++++++
4 files changed, 476 insertions(+), 57 deletions(-)
create mode 100644 drivers/infiniband/core/cm_trace.c
create mode 100644 drivers/infiniband/core/cm_trace.h
--
Chuck Lever
next reply other threads:[~2020-07-10 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 14:06 Chuck Lever [this message]
2020-07-10 14:06 ` [PATCH RFC 1/3] RDMA/core: Move the rdma_show_ib_cm_event() macro Chuck Lever
2020-07-10 14:06 ` [PATCH RFC 2/3] RDMA/cm: Replace pr_debug() call sites with tracepoints Chuck Lever
2020-07-10 14:10 ` Chuck Lever
2020-07-10 14:06 ` [PATCH RFC 3/3] RDMA/cm: Add tracepoints to track MAD send operations Chuck Lever
2020-07-10 15:17 ` [PATCH RFC 0/3] IB CM tracepoints Jason Gunthorpe
2020-07-10 16:32 ` Chuck Lever
2020-07-20 14:00 ` Jason Gunthorpe
2020-07-20 14:05 ` Chuck Lever
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=20200710135812.14749.4630.stgit@klimt.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=aron.silverton@oracle.com \
--cc=linux-rdma@vger.kernel.org \
/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).