From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
"Robert D. Russell" <rdr-zcUZCMB5SQOVc3sceRu5cw@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] libibverbs/doc: clarify selective signaling (Re: using IBV_SEND_SIGNALED)
Date: Tue, 30 Nov 2010 11:57:44 -0700 [thread overview]
Message-ID: <20101130185744.GK16788@obsidianresearch.com> (raw)
In-Reply-To: <4CF4E65D.4070205-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
On Tue, Nov 30, 2010 at 01:56:13PM +0200, Or Gerlitz wrote:
> Steve Wise wrote:
> > On 11/29/2010 11:34 AM, Robert D. Russell wrote:
> > See section 8.2.1 of the iWARP Verbs draft at:
> > http://tools.ietf.org/html/draft-hilland-rddp-verbs-00#section-8.2.1.
> > The last big paragraph in 8.2.1 spells it all out.
> > There should be a similar requirement in the IBTA IB Verbs specification...
>
> Yes, I think the below patch to the man page can help people
> understand how to work with the thing
I think the subtly here is that remote completion of a local WR does
not indiciate local completion. This is the only operational case I
can think of that might break the rules.
For instance a protocol that had remote acks for all SENDs might be
tempted to not ever use signaled WR's on the local side - since
receiving the remote ACK SEND must indicate the local SEND WR is
complete. This is the incorrect assumption.
So, I'd suggest this language:
Applications which use selective signaling can only assume that
unsignaled WRs are complete once a completion for a later signaled WR
is received. In practice this means that a signaled WR must be
used periodically, and that the send queue should never be filled with
unsignaled WRs.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-30 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1011291128190.31687@postal.iol.unh.edu>
[not found] ` <4CF3DDF0.2070907@opengridcomputing.com>
[not found] ` <alpine.LNX.2.00.1011291233540.5810@postal.iol.unh.edu>
[not found] ` <4CF3E5FA.6010308@opengridcomputing.com>
[not found] ` <4CF3E5FA.6010308-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-11-30 11:56 ` [PATCH] libibverbs/doc: clarify selective signaling (Re: using IBV_SEND_SIGNALED) Or Gerlitz
[not found] ` <4CF4E65D.4070205-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-11-30 18:57 ` Jason Gunthorpe [this message]
[not found] ` <20101130185744.GK16788-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-12-01 8:17 ` Or Gerlitz
2010-12-01 9:01 ` Or Gerlitz
[not found] ` <4CF60ED0.6000502-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-12-01 19:10 ` 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=20101130185744.GK16788@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org \
--cc=rdr-zcUZCMB5SQOVc3sceRu5cw@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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