From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] libibverbs: add path record definitions to sa.h
Date: Tue, 18 May 2010 09:03:41 -0500 [thread overview]
Message-ID: <4BF29E3D.40704@opengridcomputing.com> (raw)
In-Reply-To: <adask5pnav3.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
Roland Dreier wrote:
> > Can you add the RAW_ETY qp type in this release as well?
>
> To be honest I haven't looked at the iWARP datagram stuff at all. I'm
> not sure overloading the RAW_ETY QP type is necessarily the right thing
> to do -- it has quite different (never implemented) semantics in the IB
> case. Is there any overview of what you guys are planning as far as
> how work requests are created for such QPs?
>
The RAW_ETY qp would be just that: A kernel-bypass/user mode qp that
allows sending/receiving ethernet packets. It would also provide a way
for user applications to join/leave ethernet mcast groups (which
requires an rdma core kernel change that Intel posted too). What the
iWARP vendors are doing on top of that is implementing some form of UDP
in user mode. The main goal here is to provide an ultra low latency UDP
multicast and unicast channel for important market segments that desire
this paradigm. Also, due to the nature of this (send/recv raw eth
frames), the interface would be privileged.
If you want to wait, then later I'll post patches on how this is being
done for cxgb4. But I thought adding the RAW_ETY was definitely a
common requirement for Intel and Chelsio.
Steve.
--
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-05-18 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 22:22 [PATCH] libibverbs: add path record definitions to sa.h Sean Hefty
[not found] ` <2420730B531C4665BD842A7F46007DA2-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-06 22:33 ` Roland Dreier
[not found] ` <adapr18zmmj.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-06 23:20 ` [PATCH v2] " Sean Hefty
[not found] ` <63BD07796ED544AEAC6E41E669DC6EAC-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-12 23:07 ` Sean Hefty
[not found] ` <870D78B1ADDD407388ADBFF921BCFAC6-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-12 23:17 ` Roland Dreier
[not found] ` <ada39xwu2v9.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-12 23:21 ` Sean Hefty
2010-05-16 22:16 ` Roland Dreier
[not found] ` <adavdano5lb.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-17 13:38 ` Steve Wise
[not found] ` <4BF146F2.5060909-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-05-18 3:32 ` Roland Dreier
[not found] ` <adask5pnav3.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-18 14:03 ` Steve Wise [this message]
[not found] ` <4BF29E3D.40704-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-05-19 15:37 ` Walukiewicz, Miroslaw
[not found] ` <BE2BFE91933D1B4089447C64486040801D4D8232-IGOiFh9zz4wLt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-05-19 16:00 ` Steve Wise
[not found] ` <4BF40B09.6070809-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-05-19 21:21 ` Steve Wise
[not found] ` <4BF4565B.4040208-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-05-19 21:31 ` Sean Hefty
2010-05-21 14:58 ` Walukiewicz, Miroslaw
[not found] ` <BE2BFE91933D1B4089447C64486040801D5370A4-IGOiFh9zz4wLt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-05-21 15:03 ` Steve Wise
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=4BF29E3D.40704@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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