public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "nmoreychaisemartin-IBi9RG/b67k@public.gmane.org"
	<nmoreychaisemartin-IBi9RG/b67k@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org"
	<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Subject: Re: [RFC rdma-core 2/2] srp_daemon: fix CQ handling
Date: Mon, 11 Dec 2017 16:30:09 +0000	[thread overview]
Message-ID: <1513009807.2747.11.camel@wdc.com> (raw)
In-Reply-To: <f35bfdad-9027-d2be-9706-b5a0edd9a778-IBi9RG/b67k@public.gmane.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 763 bytes --]

On Mon, 2017-12-11 at 15:46 +0100, Nicolas Morey-Chaisemartin wrote:
> +tatic int poll_cq_once(struct sync_resources *sync_res, struct ibv_cq *cq,
> +           struct ibv_wc *wc)

Has this patch been tested? I don't think that "tatic" is a valid keyword?

> +		/* Poll CQ once. There may be extra completion that
> +		 * were associated to the previous event */
> +		ret = poll_cq_once(sync_res, cq, wc);
> +		if (ret)
> +			return ret;

How many extra completions can be associated with an event? Is polling once
sufficient? If so, please update the comment ("an" is missing / "were" ->
"was").

Thanks,

Bart.N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±­ÙšŠ{ayº\x1dʇڙë,j\a­¢f£¢·hš‹»öì\x17/oSc¾™Ú³9˜uÀ¦æå‰È&jw¨®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þ–Šàþf£¢·hšˆ§~ˆmš

  parent reply	other threads:[~2017-12-11 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 11:08 [BUG] SRP daemon and SM migration Nicolas Morey-Chaisemartin
     [not found] ` <bd47faf6-eae0-d520-42ce-eb3d6bce4376-l3A5Bk7waGM@public.gmane.org>
2017-12-04 13:50   ` Hal Rosenstock
     [not found]     ` <1978d0ad-909f-ed8b-5b54-e8c465d3641f-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-12-08  9:36       ` [RFC rdma-core] srp_daemon: handle SM lid change Nicolas Morey-Chaisemartin
     [not found]         ` <82bd1d9a-7e6a-324e-1e00-43fcf130faf0-IBi9RG/b67k@public.gmane.org>
2017-12-08 13:33           ` Hal Rosenstock
     [not found]             ` <82dc0912-3ac3-9548-2c3b-703c6e1c9c95-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-12-08 13:56               ` Dennis Dalessandro
     [not found]                 ` <dce98958-a6e2-b289-2a58-609d1914affb-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-12-08 16:41                   ` Bart Van Assche
2017-12-08 17:35               ` Nicolas Morey-Chaisemartin
2017-12-11 14:46               ` [RFC rdma-core 2/2] srp_daemon: fix CQ handling Nicolas Morey-Chaisemartin
     [not found]                 ` <f35bfdad-9027-d2be-9706-b5a0edd9a778-IBi9RG/b67k@public.gmane.org>
2017-12-11 16:30                   ` Bart Van Assche [this message]
     [not found]                     ` <1513009807.2747.11.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-11 16:38                       ` Nicolas Morey-Chaisemartin

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=1513009807.2747.11.camel@wdc.com \
    --to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
    --cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nmoreychaisemartin-IBi9RG/b67k@public.gmane.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