From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] net/null optimizations
Date: Wed, 26 Mar 2025 14:35:24 -0700 [thread overview]
Message-ID: <20250326213608.581345-1-stephen@networkplumber.org> (raw)
While reviewing use of null device for testing, noticed several things
this driver is doing which are unnecessary.
Stephen Hemminger (4):
net/null: Tx optimizations
net/null: fix packet copy
net/null: optimize Rx
net/null: count all queues
drivers/net/null/#rte_eth_null.c# | 754 ++++++++++++++++++++++++++++++
drivers/net/null/rte_eth_null.c | 95 ++--
2 files changed, 788 insertions(+), 61 deletions(-)
create mode 100644 drivers/net/null/#rte_eth_null.c#
--
2.47.2
next reply other threads:[~2025-03-26 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 21:35 Stephen Hemminger [this message]
2025-03-26 21:35 ` [PATCH 1/4] net/null: Tx optimizations Stephen Hemminger
2025-03-26 21:35 ` [PATCH 2/4] net/null: fix packet copy Stephen Hemminger
2025-03-26 21:35 ` [PATCH 3/4] net/null: optimize Rx Stephen Hemminger
2025-03-26 21:35 ` [PATCH 4/4] net/null: count all queues Stephen Hemminger
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=20250326213608.581345-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@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).