From: Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: RE: [PATCH libibverbs v5 4/7] libibverbs: Add support for XRC QPs
Date: Sun, 31 Mar 2013 11:39:30 +0300 [thread overview]
Message-ID: <5157F642.9090004@mellanox.com> (raw)
In-Reply-To: 1364332466-22786-5-git-send-email-sean.hefty () intel ! com
Hi Sean,
Just wonder, the Infiniband Annex for XRC uses the terms "XRC INI QP"
and "XRC TGT QP" and the kernel include file "include/rdma/ib_verbs.h"
also defines "IB_QPT_XRC_INI" and "IB_QPT_XRC_TGT" so why to use in
"include/infiniband/verbs.h" other names i.e. "IBV_QPT_XRC_SEND" and
"IBV_QPT_XRC_RECV"?
I agree that send and receive are more intuitive but I think that
consistency is more important.
Best regards,
S.P.
--
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 reply other threads:[~2013-03-31 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 8:39 Shlomo Pongratz [this message]
[not found] ` <5157F642.9090004-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-03-31 8:59 ` [PATCH libibverbs v5 4/7] libibverbs: Add support for XRC QPs Hefty, Sean
-- strict thread matches above, loose matches on Subject: below --
2013-03-26 21:14 [PATCH libibverbs v5 0/7] Provide verbs extension mechanism and add XRC support sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1364332466-22786-1-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-03-26 21:14 ` [PATCH libibverbs v5 4/7] libibverbs: Add support for XRC QPs sean.hefty-ral2JQCrhuEAvxtiuMwx3w
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=5157F642.9090004@mellanox.com \
--to=shlomop-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@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