DPDK usage discussions
 help / color / mirror / Atom feed
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "users@dpdk.org" <users@dpdk.org>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-users] dpdk-20.11 and shared libraries
Date: Tue, 20 Apr 2021 16:24:50 +0000
Message-ID: <3e2a222c70864e73965adbe64b5c72a2@boeing.com> (raw)

Hi, I have put a lot of time into learning about dpdk-20.11 but I have not yet found
documentation on how to use it with shared libraries.  In dpdk-20.11, the examples
are all built as "static" by default meaning that the entire kitchen sink of all DPDK
libraries are linked in during the "ld" phase and the resulting binary is huge. When
built as "static", the examples all appear to work fine as everything is loaded by
default at runtime.

When I build the examples as "shared", however, the story is completely different.
Examples that run fine as "static" do not work at all when built as "shared". It is
clear that somehow the build procedure is not giving adequate instructions to the
loader so that all necessary libraries will be ready to go at runtime.

I believe what needs to happen is that initialization code needs to be added to the
example "main.c" modules to initialize functions that will be needed by lower levels
but that are not being picked up on by the loader. But, I can find no documentation
for how to do this. In my next message, I will send a code example of what I have
tried so far.

Stephen, can you provide guidance on how to work with dpdk-20.11 in shared
library environments? I would be happy to be pointed to any documentation
I may be missing.

Thanks - Fred



             reply	other threads:[~2021-04-20 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 16:24 Templin (US), Fred L [this message]
2021-04-20 16:45 ` Templin (US), Fred L
2021-04-27  6:41 ` David Marchand

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=3e2a222c70864e73965adbe64b5c72a2@boeing.com \
    --to=fred.l.templin@boeing.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git