From: Dotan Barak <dotan-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 13:04:19 +0300 [thread overview]
Message-ID: <201106161304.19939.dotanb@sw.voltaire.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237302124E-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hi.
I noticed minor issue:
> @@ -564,6 +597,16 @@ struct ibv_srq {
> pthread_mutex_t mutex;
> pthread_cond_t cond;
> uint32_t events_completed;
> +
> + /* Following fields only available if device supports extensions */
> + enum ibv_srq_type srq_type;
> + union {
> + struct {
> + uint32_t srq_num;
> + struct ibv_xrcd *xrcd;
> + struct ibv_cq *cq;
> + } xrc;
> + } ext;
> };
Should the following struct be used instead of the suggested struct above?
struct {
struct ibv_xrcd *xrcd;
struct ibv_cq *cq;
uint32_t srq_num;
} xrc;
(attributes were rearranged according to their size).
Thanks
Dotan
--
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 10:04 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 [this message]
[not found] ` <201106161304.19939.dotanb-g2bIKuvJtcQanlnWow0HJg@public.gmane.org>
2011-06-16 15:02 ` Hefty, Sean
2011-06-16 15:05 ` Or Gerlitz
[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=201106161304.19939.dotanb@sw.voltaire.com \
--to=dotan-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@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