From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Bernard Metzler <BMT-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: WRITE_WITH_IMMEDIATE target semantic
Date: Mon, 20 Sep 2010 11:23:47 -0600 [thread overview]
Message-ID: <20100920172347.GA11157@obsidianresearch.com> (raw)
In-Reply-To: <OF2575B7D8.9367EBA3-ONC12577A4.0057C50D-C12577A4.005AD45D-Xeyd2O9EBijQT0dZR+AlfA@public.gmane.org>
On Mon, Sep 20, 2010 at 06:32:05PM +0200, Bernard Metzler wrote:
> while currently only supported by the InfiniBand transport,
> the libibverbs define a IBV_WR_RDMA_WRITE_WITH_IMM work request.
> Could someone please explain what the action at the peer side would be
> if a WRITE with immediate data comes in? One possible action would be
> to:
I've used this feature and according to my notes this is broadly
correct. A RWQE is consumed, the HCA doesn't use it for anything, and
the WC has the imm_data set, and the wr_id corrisponds to the RWQE.
The IBA notes the RWQE could be zero length.
The app needs to check for:
if (wc.opcode & IBV_WC_RECV)
To see if the completion consumed a RWQE.
> (3) set the WC's 'byte_len' to the received WRITE payload,
Hmm, I'm surprised by this, but, yep! pg 632 of the IBA.
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-09-20 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 16:32 WRITE_WITH_IMMEDIATE target semantic Bernard Metzler
[not found] ` <OF2575B7D8.9367EBA3-ONC12577A4.0057C50D-C12577A4.005AD45D-Xeyd2O9EBijQT0dZR+AlfA@public.gmane.org>
2010-09-20 17:23 ` Jason Gunthorpe [this message]
2010-09-20 17:25 ` Hefty, Sean
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=20100920172347.GA11157@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=BMT-OA+xvbQnYDHMbYB6QlFGEg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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