From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@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 4/8] livibverbs: Add support for XRC SRQs
Date: Mon, 24 Sep 2012 14:34:02 -0600 [thread overview]
Message-ID: <20120924203401.GB9472@obsidianresearch.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237346A8E801-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Sep 20, 2012 at 09:43:06PM +0000, Hefty, Sean wrote:
> @@ -1052,6 +1084,9 @@ static inline int ibv_req_notify_cq(struct ibv_cq *cq, int solicited_only)
> struct ibv_srq *ibv_create_srq(struct ibv_pd *pd,
> struct ibv_srq_init_attr *srq_init_attr);
>
> +struct ibv_srq *ibv_create_srq_ex(struct ibv_pd *pd,
> + struct ibv_srq_init_attr_ex *srq_init_attr_ex);
> +
Just to be clear here, the original proposals for this had an inline
wrapper indirecting through a function pointer here to avoid a
link-time dependency - is that something people still want?
If we are OK with a link time dependency, then do we need the new
symbol name or can we just symbol version ibv_create_srq ? (accepting
there are small problems with that..)
Jason
--
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:[~2012-09-24 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 21:43 [PATCH 4/8] livibverbs: Add support for XRC SRQs Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237346A8E801-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-09-24 20:34 ` Jason Gunthorpe [this message]
[not found] ` <20120924203401.GB9472-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-09-24 20:49 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237346A8F034-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-09-25 12:35 ` Tzahi Oved
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=20120924203401.GB9472@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@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