From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] libibverbs: Add support for XRC QPs
Date: Thu, 16 Jun 2011 18:05:28 +0300 [thread overview]
Message-ID: <4DFA1BB8.9000305@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237302124E-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hefty, Sean wrote:
> enum ibv_qp_type {
> IBV_QPT_RC = 2,
> IBV_QPT_UC,
> - IBV_QPT_UD
> + IBV_QPT_UD,
> + IBV_QPT_XRC_SEND,
> + IBV_QPT_XRC_RECV
> };
Sean,
The upstream kernel (below) uses already the values 5 and 6 for
the IB RAW qp types
> enum ib_qp_type {
> IB_QPT_SMI,
> IB_QPT_GSI,
> IB_QPT_RC,
> IB_QPT_UC,
> IB_QPT_UD,
> IB_QPT_RAW_IPV6,
> IB_QPT_RAW_ETHERTYPE
> };
ofed (below) uses 5 for XRC, 6/7 for IB raw qp types
and 8 for the new "eth packet qp", XRC and the packet QP
are used from user space with code which is out...
so if possible can we at least keep the packet qp type value
unchanged, as for XRC its different API...
> enum ib_qp_type {
> IB_QPT_SMI,
> IB_QPT_GSI,
> IB_QPT_RC,
> IB_QPT_UC,
> IB_QPT_UD,
> IB_QPT_XRC,
> IB_QPT_RAW_IPV6,
> IB_QPT_RAW_ETHERTYPE,
> IB_QPT_RAW_PACKET
--
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-16 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 17:05 [PATCH 2/2] libibverbs: Add support for XRC QPs Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237302124E-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-06-16 10:04 ` Dotan Barak
[not found] ` <201106161304.19939.dotanb-g2bIKuvJtcQanlnWow0HJg@public.gmane.org>
2011-06-16 15:02 ` Hefty, Sean
2011-06-16 15:05 ` Or Gerlitz [this message]
[not found] ` <4DFA1BB8.9000305-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-06-16 15:09 ` Or Gerlitz
2011-06-16 16:03 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373021813-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-06-16 18:06 ` Or Gerlitz
[not found] ` <BANLkTi=r5kG4rUH1+dsgOg1LcdrzZRA_Ew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-16 19:07 ` 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=4DFA1BB8.9000305@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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