From: David Marchand <david.marchand@redhat.com>
To: "Alipour, Mehrdad" <malipour@ciena.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [**EXTERNAL**] Re: rte_mempool_create fails with --no-huge
Date: Fri, 6 Dec 2024 08:38:10 +0100 [thread overview]
Message-ID: <CAJFAV8y2WkMWpBKZmQkosKMLJwUnD-BDgtsw3GXxAcLNeUhJGA@mail.gmail.com> (raw)
In-Reply-To: <DM6PR04MB6761C3B323654A7414D8ED49C4302@DM6PR04MB6761.namprd04.prod.outlook.com>
On Thu, Dec 5, 2024 at 10:28 PM Alipour, Mehrdad <malipour@ciena.com> wrote:
>
> Hello David/Dmitry,
>
> After adding -d <path_of_drivers>, I can now see all the pmd shared libs loading fine and rte_mempool_create works with --no-huge.
Adding -d should be unneeded with a properly installed DPDK.
You should double check what I mentionned (esp. RTE_EAL_PMD_PATH must
match the pmd install path on your host).
--
David Marchand
prev parent reply other threads:[~2024-12-06 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:54 Alipour, Mehrdad
2024-12-04 20:51 ` Dmitry Kozlyuk
2024-12-04 23:05 ` [**EXTERNAL**] " Alipour, Mehrdad
2024-12-05 8:30 ` David Marchand
2024-12-05 21:28 ` Alipour, Mehrdad
2024-12-06 7:38 ` David Marchand [this message]
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=CAJFAV8y2WkMWpBKZmQkosKMLJwUnD-BDgtsw3GXxAcLNeUhJGA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=malipour@ciena.com \
/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).