From: Jakub Kicinski <kuba@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCHv2 net-next] net: ucc_geth: Batch RX packets before stack handoff
Date: Mon, 25 May 2026 12:47:40 -0700 [thread overview]
Message-ID: <20260525124740.5e71e96c@kernel.org> (raw)
In-Reply-To: <20260521060729.2293222-1-rosenp@gmail.com>
On Wed, 20 May 2026 23:07:29 -0700 Rosen Penev wrote:
> It would be nice to use napi_gro_receive, but the tradeoff is lower
> routing performance. There is no support for hardware checksum offload,
> which really hurts routing performance.
Not sure this was clear from the previous discussion but AFAIK
GRO will fall back to the list processing if disabled with ethtool -K
So the argument of GRO-enabled being slower for forwarding is moot.
--
pw-bot: cr
prev parent reply other threads:[~2026-05-25 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 6:07 [PATCHv2 net-next] net: ucc_geth: Batch RX packets before stack handoff Rosen Penev
2026-05-25 19:47 ` Jakub Kicinski [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=20260525124740.5e71e96c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.