From: Jason Gunthorpe <jgg@ziepe.ca>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Leon Romanovsky <leon@kernel.org>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v6 2/2] RDMA/cma: Add trace points in RDMA Connection Manager
Date: Tue, 19 Nov 2019 13:00:38 -0400 [thread overview]
Message-ID: <20191119170038.GD4991@ziepe.ca> (raw)
In-Reply-To: <6F70DF6D-B73A-490D-B344-1F216D1B222F@oracle.com>
On Tue, Nov 19, 2019 at 07:10:03AM -0500, Chuck Lever wrote:
> >> diff --git a/include/trace/events/rdma_cma.h b/include/trace/events/rdma_cma.h
> >> new file mode 100644
> >> index 000000000000..b6ccdade651c
> >> +++ b/include/trace/events/rdma_cma.h
> >> @@ -0,0 +1,218 @@
> >> +/* SPDX-License-Identifier: GPL-2.0-only */
> >> +/*
> >> + * Trace point definitions for the RDMA Connect Manager.
> >> + *
> >> + * Author: Chuck Lever <chuck.lever@oracle.com>
> >> + *
> >> + * Copyright (c) 2019, Oracle and/or its affiliates. All rights reserved.
> >> + */
> >> +
> >> +#undef TRACE_SYSTEM
> >> +#define TRACE_SYSTEM rdma_cma
> >> +
> >> +#if !defined(_TRACE_RDMA_CMA_H) || defined(TRACE_HEADER_MULTI_READ)
> >> +
> >> +#define _TRACE_RDMA_CMA_H
> >> +
> >> +#include <linux/tracepoint.h>
> >> +#include <rdma/rdma_cm.h>
> >> +#include "cma_priv.h"
> >
> > Did it compile?
>
> Yes, it compiles for me, and passes lkp as well.
>
> I admit though that it seems like a brittle arrangement. Might be
> better off moving rdma_cma.h to drivers/infiniband/core/ .
The more headers that can move out of include the better, IMHO
Jason
prev parent reply other threads:[~2019-11-19 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 21:49 [PATCH v6 0/2] Proposed trace points for RDMA/core Chuck Lever
2019-11-18 21:49 ` [PATCH v6 1/2] RDMA/core: Trace points for diagnosing completion queue issues Chuck Lever
2019-11-19 17:01 ` Jason Gunthorpe
2019-11-19 17:07 ` Chuck Lever
2019-11-18 21:49 ` [PATCH v6 2/2] RDMA/cma: Add trace points in RDMA Connection Manager Chuck Lever
2019-11-19 7:45 ` Leon Romanovsky
2019-11-19 9:18 ` Zengtao (B)
2019-11-19 12:10 ` Chuck Lever
2019-11-19 17:00 ` Jason Gunthorpe [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=20191119170038.GD4991@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=chuck.lever@oracle.com \
--cc=leon@kernel.org \
--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).