From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH libibverbs] Fix create/destroy flow API
Date: Fri, 4 Sep 2015 17:51:11 -0400 [thread overview]
Message-ID: <55EA124F.2070305@redhat.com> (raw)
In-Reply-To: <20150904213226.GB20758-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On 09/04/2015 05:32 PM, Jason Gunthorpe wrote:
> On Fri, Sep 04, 2015 at 05:17:38PM -0400, Doug Ledford wrote:
>> + /*
>> + * In order to maintain backward/forward binary compatibility
>> + * with libmlx4-1.0.6, which has the original version of the
>> + * flow steering patches, we need to set the two
>> + * ABI_compat_placeholder entries to match the driver
>> + * set flow entries. This is because, in the specific instance
>> + * of using libmlx4-1.0.6 with the fixed version of
>> + * libibvberbs, the ibv_create_flow inline function already
>> + * compiled into libmlx4-1.0.6 will be loooking in the
>> + * ABI_placeholder spots for the function pointer to the
>> + * create and destroy flow verbs.
>> */
>
> This isn't quite the right comment, it has very little to do with mlx,
> ibv_create_flow is the user entry point, the above applies to
> everything linked to ibverbs.
You're right. I'll correct that.
> My suggestion was to not change the ibverbs->user ABI at all and just
> mangle the driver side, ie move the ABI_placeholder to what was drv_
> instead of lib_.
As you pointed out, this doesn't make the entire matrix of old/new
driver/libibverbs/app work. I can think of two things that would be
ugly about doing it this way if we wanted to make that matrix fully
operational. With the way I did it, things are clean in the new driver
and mostly clean in the new libibverbs, and the full matrix works.
> Can't see anything wrong with it this way, off hand, other than the
> comment.
Thanks for looking at it ;-)
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-09-04 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 21:17 [PATCH libibverbs] Fix create/destroy flow API Doug Ledford
[not found] ` <9665e46a71940f2721b30fdb4aaa0853161babc9.1441401379.git.dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-04 21:32 ` Jason Gunthorpe
[not found] ` <20150904213226.GB20758-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-09-04 21:51 ` Doug Ledford [this message]
[not found] ` <55EA124F.2070305-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-04 21:59 ` Doug Ledford
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=55EA124F.2070305@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.