From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Alex Rosenbaum <Alexr-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: Re: Name for a new type of QP
Date: Wed, 23 Jun 2010 14:27:24 +0300 [thread overview]
Message-ID: <4C21EF9C.1020304@voltaire.com> (raw)
In-Reply-To: <7E95F01E94AB484F83061FCFA35B39F868D9D2-QfUkFaTmzUSUvQqKE/ONIwC/G2K4zDHf@public.gmane.org>
Alex Rosenbaum wrote:
> I never fully understood what does IBV_QPT_RAW_ETY stand for? Maybe we should change its name to better represent what the code does.
before, maybe take a look on the IB spec... see the spec references
mentioned by the patch to support IB_QPT_RAW_ETY which posted to the
list in the past, but didn't make it to upstream yet @
http://lists.openfabrics.org/pipermail/general/2008-December/055954.html
Also, IBA chapter 2, states that "Raw Datagram - A packet that contains
an IBA Local Route Header, may contain an IBA Global Route Header, but
does not contain an IBA Transport header, and is not handled by IBA
transport services",
&& chapter 3, section 3.6.2 "IBA TRANSPORT SERVICES" explains everything
in detail, including what is the difference between raw ethernet to raw
ipv6, look for "The Raw Datagram service is not technically a transport
but rather it is a data link service that allows a QP to send and
receive raw datagram messages" and following text.
Or.
Or.
--
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-06-23 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 9:19 Name for a new type of QP Moni Shoua
[not found] ` <4C21D1AA.8060402-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2010-06-23 10:20 ` Walukiewicz, Miroslaw
[not found] ` <BE2BFE91933D1B4089447C64486040801E9D892A-IGOiFh9zz4wLt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-06-23 11:03 ` Alex Rosenbaum
[not found] ` <7E95F01E94AB484F83061FCFA35B39F868D9D2-QfUkFaTmzUSUvQqKE/ONIwC/G2K4zDHf@public.gmane.org>
2010-06-23 11:27 ` Or Gerlitz [this message]
2010-06-23 17:58 ` Roland Dreier
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=4C21EF9C.1020304@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=Alexr-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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