From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: users <users@dpdk.org>
Subject: Rx performance
Date: Wed, 16 Jul 2025 12:29:28 +0000 [thread overview]
Message-ID: <CH3PR01MB847019A1426FDBCD8D4C3F0F8F56A@CH3PR01MB8470.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi,
I have E810-C 2x100G NIC, the perf tool shows scalar rx path and not vectorized rx path. When I turn off Rx Offload (NIC rx timestamp) I see vectorized rx path in perf tool.
Why is this a drawback and is this with just the E810 NIC?
is there a way around this so Rx Offload Rx Timestamp can be used in our application and get vectorized rx path?
We need rx timestamps of packets and max performance.
Thanks,
Ed
[-- Attachment #2: Type: text/html, Size: 730 bytes --]
next reply other threads:[~2025-07-16 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 12:29 Lombardo, Ed [this message]
2025-07-16 12:45 ` Ivan Malov
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=CH3PR01MB847019A1426FDBCD8D4C3F0F8F56A@CH3PR01MB8470.prod.exchangelabs.com \
--to=ed.lombardo@netscout.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).