From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Steven Dake <sdake-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Benoit Hudzia
<benoit.hudzia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: need pointer to Understand how to use IBV_WR_RDMA_WRITE_WITH_IMM
Date: Tue, 07 Jun 2011 11:36:52 -0500 [thread overview]
Message-ID: <4DEE53A4.3080409@opengridcomputing.com> (raw)
In-Reply-To: <20110607163111.GA24005-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On 06/07/2011 11:31 AM, Jason Gunthorpe wrote:
> On Tue, Jun 07, 2011 at 07:18:14AM -0700, Steven Dake wrote:
>> On 06/07/2011 05:23 AM, Benoit Hudzia wrote:
>>> I am uncertain if this is the correct place for such email, please
>>> point me to an appropriate mailing list place if not.
>>>
>>> I would like to use IBV_WR_RDMA_WRITE_WITH_IMM , however I am facing
>>> difficulty to find documentation or example on how to use such
>>> feature. The idea would be to do an RDMA write and wake up the peer
>>> upon reception in order to process the received data.
>>>
>>> What I understand from IBV_WR_RDMA_WRITE_WITH_IMM:
>> I would recommend against using IMM modes. I believe they are not
>> supported on non-infiniband hardware, which limits your application from
>> being used on Ethernet rdma systems.
> There is some talk of fixing that in iWarp, the IMM stuff is much more
> efficient than a RDMA + SEND combo.
>
iWARP 2.0: http://datatracker.ietf.org/doc/draft-ietf-storm-rdmap-ext/
> If you are going to use it, and care about iWarp then you should
> design a fall back into your protocol to use RDMA + SEND.. I have some
> stuff that works like this.
>
> 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
--
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:[~2011-06-07 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:23 need pointer to Understand how to use IBV_WR_RDMA_WRITE_WITH_IMM Benoit Hudzia
[not found] ` <BANLkTikC6jPFJm=MxT5oNDoJH4Ex+j41XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-07 14:18 ` Steven Dake
[not found] ` <4DEE3326.9050105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-07 16:31 ` Jason Gunthorpe
[not found] ` <20110607163111.GA24005-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-06-07 16:36 ` Steve Wise [this message]
2011-06-07 14:23 ` Hefty, Sean
2011-06-07 16:43 ` Jason Gunthorpe
[not found] ` <20110607164333.GB24005-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-06-08 18:35 ` Benoit Hudzia
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=4DEE53A4.3080409@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=benoit.hudzia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sdake-H+wXaHxf7aLQT0dZR+AlfA@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