From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Ralph Campbell <ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: Tom Tucker <tom-/Yg/VP3ZvrM@public.gmane.org>,
"rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org"
<rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"brandt-4OHPYypu0djtX7QSmKvirg@public.gmane.org"
<brandt-4OHPYypu0djtX7QSmKvirg@public.gmane.org>,
"swise-/Yg/VP3ZvrM@public.gmane.org"
<swise-/Yg/VP3ZvrM@public.gmane.org>
Subject: Re: [RFC PATCH 3/3] libibverbs: Add reg/unreg I/O memory verbs
Date: Thu, 29 Jul 2010 14:19:44 -0600 [thread overview]
Message-ID: <20100729201944.GB7920@obsidianresearch.com> (raw)
In-Reply-To: <1280434056.6820.136.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
On Thu, Jul 29, 2010 at 01:07:36PM -0700, Ralph Campbell wrote:
> > @@ -640,6 +640,9 @@ struct ibv_context_ops {
> > size_t length,
> > int access);
> > int (*dereg_mr)(struct ibv_mr *mr);
> > + struct ibv_mr * (*reg_io_mr)(struct ibv_pd *pd, void *addr, size_t length,
> > + int access);
> > + int (*dereg_io_mr)(struct ibv_mr *mr);
> > struct ibv_mw * (*alloc_mw)(struct ibv_pd *pd, enum ibv_mw_type type);
> > int (*bind_mw)(struct ibv_qp *qp, struct ibv_mw *mw,
> > struct ibv_mw_bind *mw_bind);
>
> Doesn't adding these in the middle of the struct break the
> libibverbs to libxxxverbs.so binary interface?
> Shouldn't they be added at the end of the struct?
> I'm not sure how the versioning works between libibverbs and
> device plugins. Don't we need to protect against libibverbs
> being upgraded but the libxxxverbs.so being older?
Adding them at all, anywhere, breaks the ABI, and needs a soname bump
of libibverbs. Last time this was done a versioned symbol approach was
used to try and keep handling a 1.0 ibv_context structure, but that
only works some times and breaks in corner cases :(
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:[~2010-07-29 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 16:31 [RFC PATCH 0/3] libibverbs: Add I/O memory registration verbs Tom Tucker
[not found] ` <20100729163030.14901.87547.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-07-29 16:31 ` [RFC PATCH 1/3] libibverbs: Fix libtool configure warning Tom Tucker
2010-07-29 16:31 ` [RFC PATCH 2/3] libibverbs: Add reg/unreg I/O memory commands to kern ABI Tom Tucker
2010-07-29 16:32 ` [RFC PATCH 3/3] libibverbs: Add reg/unreg I/O memory verbs Tom Tucker
[not found] ` <20100729163202.14901.44211.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-07-29 20:07 ` Ralph Campbell
[not found] ` <1280434056.6820.136.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
2010-07-29 20:19 ` Jason Gunthorpe [this message]
2010-07-29 20:32 ` Tom Tucker
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=20100729201944.GB7920@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=brandt-4OHPYypu0djtX7QSmKvirg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=swise-/Yg/VP3ZvrM@public.gmane.org \
--cc=tom-/Yg/VP3ZvrM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.