All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH v6 1/2] RDMA/core: Trace points for diagnosing completion queue issues
Date: Tue, 19 Nov 2019 13:01:41 -0400	[thread overview]
Message-ID: <20191119170141.GE4991@ziepe.ca> (raw)
In-Reply-To: <20191118214906.27891.14380.stgit@manet.1015granger.net>

On Mon, Nov 18, 2019 at 04:49:09PM -0500, Chuck Lever wrote:
> @@ -65,11 +68,35 @@ static void rdma_dim_init(struct ib_cq *cq)
>  	INIT_WORK(&dim->work, ib_cq_rdma_dim_work);
>  }
>  
> +/**
> + * ib_poll_cq - poll a CQ for completion(s)
> + * @cq: the CQ being polled
> + * @num_entries: maximum number of completions to return
> + * @wc: array of at least @num_entries &struct ib_wc where completions
> + *      will be returned
> + *
> + * Poll a CQ for (possibly multiple) completions.  If the return value
> + * is < 0, an error occurred.  If the return value is >= 0, it is the
> + * number of completions returned.  If the return value is
> + * non-negative and < num_entries, then the CQ was emptied.
> + */
> +int ib_poll_cq(struct ib_cq *cq, int num_entries, struct ib_wc *wc)
> +{
> +	int rc;
> +
> +	rc = cq->device->ops.poll_cq(cq, num_entries, wc);
> +	trace_cq_poll(cq, num_entries, rc);
> +	return rc;
> +}
> +EXPORT_SYMBOL(ib_poll_cq);

Back to the non-inlined function?

Jason

  reply	other threads:[~2019-11-19 17:01 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 [this message]
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

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=20191119170141.GE4991@ziepe.ca \
    --to=jgg@ziepe.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.