From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexander Lobakin <alexandr.lobakin@intel.com>,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/3] gro: some minor optimization
Date: Thu, 3 Feb 2022 16:48:20 +0100 [thread overview]
Message-ID: <cover.1643902526.git.pabeni@redhat.com> (raw)
This series collects a few small optimization for the GRO engine.
I measure a 10% performance improvements in micro-benchmarks
around dev_gro_receive(), but deltas are within noise range in tput
tests.
Still with big TCP coming every cycle saved from the GRO engine will
count - I hope ;)
The only change from the RFC is in patch 2, as per Alexander feedback
Paolo Abeni (3):
net: gro: avoid re-computing truesize twice on recycle
net: gro: minor optimization for dev_gro_receive()
net: gro: register gso and gro offload on separate lists
include/linux/netdevice.h | 3 +-
include/net/gro.h | 52 +++++++++---------
net/core/gro.c | 109 +++++++++++++++++++++-----------------
3 files changed, 91 insertions(+), 73 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-03 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 15:48 Paolo Abeni [this message]
2022-02-03 15:48 ` [PATCH net-next 1/3] net: gro: avoid re-computing truesize twice on recycle Paolo Abeni
2022-02-03 16:16 ` Alexander Lobakin
2022-02-03 15:48 ` [PATCH net-next 2/3] net: gro: minor optimization for dev_gro_receive() Paolo Abeni
2022-02-03 16:09 ` Alexander Lobakin
2022-02-03 16:39 ` Alexander H Duyck
2022-02-03 17:44 ` Paolo Abeni
2022-02-03 15:48 ` [PATCH net-next 3/3] net: gro: register gso and gro offload on separate lists Paolo Abeni
2022-02-03 16:11 ` Eric Dumazet
2022-02-03 16:26 ` Alexander Lobakin
2022-02-03 16:41 ` Eric Dumazet
2022-02-03 18:07 ` Paolo Abeni
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=cover.1643902526.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=alexandr.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).