DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Add more lcores to application after rte_eal_init has been called
Date: Wed, 22 Feb 2023 07:03:59 -0800	[thread overview]
Message-ID: <20230222070359.3e45d6b6@hermes.local> (raw)
In-Reply-To: <CAO8pfFkCu+E9=iwj5LG2AZ=CZRPYOqDRjZ_svGK6ZeVotym1HQ@mail.gmail.com>

On Wed, 22 Feb 2023 14:10:20 +0100
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:

> I need to add some more cores to the application after the DPDK has
> already been initialised.
> Is it possible?

No

> For other resources like network cards, I managed to probe new cards
> dynamically but don't understand how I can do the same for new lcores.

You can start with lots of cores, but only use some of them in your
application. The unused queues could wait on something like pthread_condition
that is blocking.

  reply	other threads:[~2023-02-22 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 13:10 Antonio Di Bacco
2023-02-22 15:03 ` Stephen Hemminger [this message]
2023-02-27  9:02   ` 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=20230222070359.3e45d6b6@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=a.dibacco.ks@gmail.com \
    --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).