From: Stephen Hemminger <stephen@networkplumber.org>
To: Amy Smith <gsonvin@yahoo.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Can independent dpdk applications in 2 separate pod use same cpu.
Date: Sat, 9 Sep 2023 07:46:20 -0700 [thread overview]
Message-ID: <20230909074620.2803d7ce@hermes.local> (raw)
In-Reply-To: <1346556956.3870791.1694264663662@mail.yahoo.com>
On Sat, 9 Sep 2023 13:04:23 +0000 (UTC)
Amy Smith <gsonvin@yahoo.com> wrote:
> Hi,I have 2 independent dpdk application pods working now using different set of cpu cores. For low cost use case I would like them to use same cpu. I have 1 cpu core which I want both pods to share. Is it possible? Do I need to make any changes to applications to use non eal thread, changes to scheduling thread etc.Thanks!
Possible yes, but will kill performance since most DPDK applications do pure polling.
What will happen is one application will run until preempted by the kernel scheduler, then the other one.
The preemption happens on clock tick so each one will run until the clock interrupt (usually 4 ms).
And the overhead of context switching and cache misses.
prev parent reply other threads:[~2023-09-09 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1346556956.3870791.1694264663662.ref@mail.yahoo.com>
2023-09-09 13:04 ` Amy Smith
2023-09-09 14:46 ` Stephen Hemminger [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=20230909074620.2803d7ce@hermes.local \
--to=stephen@networkplumber.org \
--cc=gsonvin@yahoo.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).