From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Robert Hable <Robert.Hable@spusu.at>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: rte_eth_dev_count_avail returns different value in library
Date: Fri, 28 Oct 2022 13:48:08 +0300 [thread overview]
Message-ID: <20221028134808.78435c9d@sovereign> (raw)
In-Reply-To: <PAXP190MB174125BF2117E20B260F21A4E1329@PAXP190MB1741.EURP190.PROD.OUTLOOK.COM>
2022-10-28 09:45 (UTC+0000), Robert Hable:
> Hello,
>
> I am trying to build a static library based on the skeleton example. My problem is when calling rte_eth_dev_count_avail() I always receive 0 in the static library. When I start the skeleton example app as a regular exe file, then it returns 2.
> What could be the reason that rte_eth_dev_count_avail() returns different values depending on if it is an exe application or a static library?
>
> rte_eal_init() is called in both applications with the default parameters.
> Both processes are running under the same administrator user.
>
> I am using Windows Server 2022 with a Mellanox ConnectX-4 on DPDK V 22.11.0-rc0.
>
> Kind regards,
> Robert Hable
>
Hi Robert,
Are you building DPDK as static libraries?
Shared build is currently non-functional on Windows.
If so, are you linking PMD libraries (librte_common_mlx5, librte_net_mlx5)
to the application that is using your static library?
If relevant PMD libraries are not linked, HW will not be discovered
(same for mempools BTW).
It is irrelevant from where rte_eth_dev_count_avail() is called,
but please check that in both cases it is done after rte_eal_init().
next prev parent reply other threads:[~2022-10-28 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 9:45 Robert Hable
2022-10-28 10:48 ` Dmitry Kozlyuk [this message]
2022-11-11 13:51 ` AW: " Robert Hable
2022-11-11 14:48 ` Dmitry Kozlyuk
2022-11-17 9:17 ` AW: " Robert Hable
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=20221028134808.78435c9d@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=Robert.Hable@spusu.at \
--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
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;
as well as URLs for NNTP newsgroup(s).