From: Leon Romanovsky <leon@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH v7 2/2] RDMA/cma: Add trace points in RDMA Connection Manager
Date: Wed, 20 Nov 2019 08:29:35 +0200 [thread overview]
Message-ID: <20191120062935.GL52766@unreal> (raw)
In-Reply-To: <20191120004606.5860.87252.stgit@manet.1015granger.net>
On Tue, Nov 19, 2019 at 07:46:06PM -0500, Chuck Lever wrote:
> Record state transitions as each connection is established. The IP
> address of both peers and the Type of Service is reported. These
> trace points are not in performance hot paths.
>
> Also, record each cm_event_handler call to ULPs. This eliminates the
> need for each ULP to add its own similar trace point in its CM event
> handler function.
>
> These new trace points appear in a new trace subsystem called
> "rdma_cma".
>
> Sample events:
>
> kworker/u24:2-2127 [011] 696.746254: cm_event_handler: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0 ADDR_RESOLVED (0/0)
> kworker/u24:2-2127 [011] 696.746880: cm_event_handler: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0 ROUTE_RESOLVED (2/0)
> kworker/u28:2-2214 [001] 696.776316: cm_send_req: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0 qp_num=526
> kworker/1:3-972 [001] 696.777603: cm_send_mra: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0
> kworker/1:3-972 [001] 696.778062: cm_send_rtu: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0
> kworker/1:3-972 [001] 696.778198: cm_event_handler: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0 ESTABLISHED (9/0)
> kworker/1:3-972 [001] 700.621750: cm_disconnect: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0
> kworker/1:3-972 [001] 700.621881: cm_sent_dreq: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0
> kworker/3:2-512 [003] 700.622354: cm_event_handler: cm_id.id=1 src: 192.168.2.51:57696 dst: 192.168.2.55:20049 tos=0 DISCONNECTED (10/0)
>
> Some features to note:
> - restracker ID of the rdma_cm_id is tagged on each trace event
> - The source and destination IP addresses and TOS are reported
> - CM event upcalls are shown with decoded event and status
> - CM state transitions are reported
>
> This patch is based on previous work by:
>
> Saeed Mahameed <saeedm@mellanox.com>
> Mukesh Kacker <mukesh.kacker@oracle.com>
> Ajaykumar Hotchandani <ajaykumar.hotchandani@oracle.com>
> Aron Silverton <aron.silverton@oracle.com>
> Avinash Repaka <avinash.repaka@oracle.com>
> Somasundaram Krishnasamy <somasundaram.krishnasamy@oracle.com>
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> drivers/infiniband/core/Makefile | 2
> drivers/infiniband/core/cma.c | 59 +++++++--
> drivers/infiniband/core/cma_trace.c | 16 +++
> drivers/infiniband/core/cma_trace.h | 219 +++++++++++++++++++++++++++++++++++
> 4 files changed, 279 insertions(+), 17 deletions(-)
> create mode 100644 drivers/infiniband/core/cma_trace.c
> create mode 100644 drivers/infiniband/core/cma_trace.h
Chuck, thanks for the updated commit message, the patches look very good.
Unfortunately, I wasn't able to compile latest series as well.
_ kernel git:(24005116b337) mkt build
Start kernel compilation in silent mode
In file included from drivers/infiniband/core/cma_trace.h:219,
from drivers/infiniband/core/cma_trace.c:16:
./include/trace/define_trace.h:95:42: fatal error: ./cma_trace.h: No such file or directory
95 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
| ^
compilation terminated.
make[3]: *** [scripts/Makefile.build:265: drivers/infiniband/core/cma_trace.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [scripts/Makefile.build:509: drivers/infiniband/core] Error 2
make[1]: *** [scripts/Makefile.build:509: drivers/infiniband] Error 2
make: *** [Makefile:1649: drivers] Error 2
_ kernel git:(173822da8f6f) git l -n 3
173822da8f6f (HEAD) RDMA/cma: Add trace points in RDMA Connection Manager
24005116b337 RDMA/core: Trace points for diagnosing completion queue issues
a25984f3baaa (rdma/wip/jgg-for-next) RDMA/qedr: Fix null-pointer dereference when calling rdma_user_mmap_get_offset
Thanks
prev parent reply other threads:[~2019-11-20 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 0:45 [PATCH v7 0/2] Proposed trace points for RDMA/core Chuck Lever
2019-11-20 0:46 ` [PATCH v7 1/2] RDMA/core: Trace points for diagnosing completion queue issues Chuck Lever
2019-11-20 0:46 ` [PATCH v7 2/2] RDMA/cma: Add trace points in RDMA Connection Manager Chuck Lever
2019-11-20 6:29 ` Leon Romanovsky [this message]
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=20191120062935.GL52766@unreal \
--to=leon@kernel.org \
--cc=chuck.lever@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).