From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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>,
"roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org"
<roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>
Subject: Re: [PATCH libibverbs v5 3/7] livibverbs: Add support for XRC SRQs
Date: Tue, 04 Jun 2013 09:13:55 -0500 [thread overview]
Message-ID: <51ADF623.9080008@opengridcomputing.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A823736FD2CB36-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 6/3/2013 6:30 PM, Hefty, Sean wrote:
>>> enum verbs_context_mask {
>>> VERBS_CONTEXT_XRCD = 1 << 0,
>>> - VERBS_CONTEXT_RESERVED = 1 << 1
>>> + VERBS_CONTEXT_SRQ = 1 << 1,
>>> + VERBS_CONTEXT_RESERVED = 1 << 2
>>> };
>> Would VERBS_CONTEXT_XSRQ or VERBS_CONTEXT_SRQ_EX be more clear?
> The structure being extended is ibv_srq, so I think just 'SRQ' is clearer. The same holds for VERBS_CONTEXT_QP.
>
> - Sean
k. Will you be posting a new series soon for libibverbs and libmlx4
against the new releases? The old series' do not apply...
thanks,
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:[~2013-06-04 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 1/7] Infrastructure to support verbs extensions sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-03-26 21:14 ` [PATCH libibverbs v5 2/7] libibverbs: Introduce XRC domains sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-03-26 21:14 ` [PATCH libibverbs v5 3/7] livibverbs: Add support for XRC SRQs sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1364332466-22786-4-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-06-03 21:05 ` Steve Wise
[not found] ` <51AD0528.6000900-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-06-03 23:30 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736FD2CB36-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-06-04 14:13 ` Steve Wise [this message]
2013-03-26 21:14 ` [PATCH libibverbs v5 4/7] libibverbs: Add support for XRC QPs sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-03-26 21:14 ` [PATCH libibverbs v5 5/7] libibverbs: Add ibv_open_qp sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1364332466-22786-6-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-05-20 17:13 ` Steve Wise
[not found] ` <519A59B1.9080402-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-05-20 17:59 ` Hefty, Sean
2013-03-26 21:14 ` [PATCH libibverbs v5 6/7] libibverbs: Add man page for ibv_open_qp sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-03-26 21:14 ` [PATCH libibverbs v5 7/7] libibverbs: Add XRC sample application 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=51ADF623.9080008@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@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