From: Bruce Richardson <bruce.richardson@intel.com>
To: Prashant Upadhyaya <praupadhyaya@gmail.com>
Cc: <dev@dpdk.org>
Subject: Re: Regarding DPDK API's like rte_timer_subsystem_init/rte_hash_create etc. in VPP
Date: Thu, 30 Mar 2023 09:00:28 +0100 [thread overview]
Message-ID: <ZCVBnM4Wdq1yFcoo@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAPBAu3UzEV7YE2n3Omv++wXjFXOGFfQanbvHi9gV1PnrJbC9Fw@mail.gmail.com>
On Thu, Mar 30, 2023 at 10:30:24AM +0530, Prashant Upadhyaya wrote:
> Hi,
>
> While trying to port some code to VPP (which uses DPDK as the backend
> driver), I am running into a problem that calls to API's like
> rte_timer_subsystem_init, rte_hash_create are failing while allocation
> of memory.
>
> This is presumably because VPP inits the EAL with the following arguments --
>
> -in-memory --no-telemetry --file-prefix vpp
>
> Is there is something that can be done eg. passing some more parms in
> the EAL initialization which hopefully wouldn't break VPP but will
> also be friendly to the RTE timer and hash functions too, that would
> be great, so requesting some advice here.
>
Hi,
can you provide some more details on what the errors are that you are
receiving? Have you been able to dig a little deeper into what might be
causing the memory failures? The above flags alone are unlikely to cause
issues with hash or timer libraries, for example.
/Bruce
next prev parent reply other threads:[~2023-03-30 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 5:00 Prashant Upadhyaya
2023-03-30 8:00 ` Bruce Richardson [this message]
2023-03-30 8:27 ` Prashant Upadhyaya
2023-03-30 9:20 ` Bruce Richardson
2023-03-30 13:12 ` Prashant Upadhyaya
2023-03-30 13:17 ` Bruce Richardson
2023-03-30 13:37 ` Prashant Upadhyaya
2023-03-30 14:02 ` Bruce Richardson
2023-03-31 9:41 ` Prashant Upadhyaya
2023-03-31 10:49 ` Bruce Richardson
2023-04-14 4:25 ` Prashant Upadhyaya
2023-04-14 9:07 ` Bruce Richardson
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=ZCVBnM4Wdq1yFcoo@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=praupadhyaya@gmail.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).