From: Stephen Hemminger <stephen@networkplumber.org>
To: Illayaraja M <illayaraj02@gmail.com>
Cc: dev@dpdk.org
Subject: Re: dpdk l2fwd performance issue in VM
Date: Tue, 22 Nov 2022 09:24:23 -0800 [thread overview]
Message-ID: <20221122092423.6ab22911@hermes.local> (raw)
In-Reply-To: <CAJDjCCDt=Au6PDqhTqg8-xhUxXk35hSTwyk-RFjrYczbx2krXQ@mail.gmail.com>
On Tue, 22 Nov 2022 11:17:48 +0530
Illayaraja M <illayaraj02@gmail.com> wrote:
> I have two l2fwd applications namely P1 and P2. P1 receives the external
> traffic and sends it to P2 and P2 simply changes the mac address and sends
> it back to P1. Finally P1 sends the packet out to the external network.
> With the above setup I'm able to achieve only 330Mbps traffic without
> packet loss.
Is the VM running with dedicated CPU's?
Each application running with dedicated virtual CPU's?
Which hypervisor?
Which virtual NIC/
Sending packets between applications always causes one or more cache misses.
And the memory bandwidth can be a limiting factor.
prev parent reply other threads:[~2022-11-22 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 5:47 Illayaraja M
2022-11-22 17:24 ` 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=20221122092423.6ab22911@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=illayaraj02@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).