From: "Bob Pearson" <rpearson-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: libverbs version confusion
Date: Thu, 21 Oct 2010 01:00:55 -0500 [thread overview]
Message-ID: <000001cb70e5$53755050$fa5ff0f0$@systemfabricworks.com> (raw)
I have an application that links to -libverbs (1.5.2) and for some reason
ibv_open_device goes to the compat 1.0 version not the default one. Other
apps in the same development tree and the standard ones like ib_send_bw all
link to __ibv_open_device which is the default on the same system. Who or
what decides which version of the symbol get linked? I have looked
everywhere and haven't found a clue yet. [BTW the calls to libibverbs are in
a shared application library that is itself linked into the application.
That library has no versioning. I compared to librdmacm which also depends
on libibverbs but there was nothing there mentioning the version of the
libibverbs api.]
It turns out that __ibv_open_device_1_0 returns a context struct that sort
of looks the same except that the cmd_fd is left uninitialized but the
version 1.1 context is passed as real_ctx. Subsequent calls to ibv_xxx fail
because the cmd_fd is uninitialized and has a random (large) value. Is
someone else supposed to fill in the rest of the fields in the 1.0 version
of the ibv_context?
Bob
--
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 reply other threads:[~2010-10-21 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 6:00 Bob Pearson [this message]
2010-10-21 16:48 ` libverbs version confusion Jason Gunthorpe
[not found] ` <20101021164812.GD30648-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-21 18:19 ` Bob Pearson
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='000001cb70e5$53755050$fa5ff0f0$@systemfabricworks.com' \
--to=rpearson-klaocwyjdxkshymvu7je4pqqe7ycjdx5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox