From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
alexanderduyck@fb.com
Subject: Re: [PATCH net-next v3] eth: fbnic: support TCP segmentation offload
Date: Tue, 25 Feb 2025 12:15:36 -0500 [thread overview]
Message-ID: <Z736uO_DiO1fkn53@LQ3V64L9R2> (raw)
In-Reply-To: <20250216174109.2808351-1-kuba@kernel.org>
On Sun, Feb 16, 2025 at 09:41:09AM -0800, Jakub Kicinski wrote:
> Add TSO support to the driver. Device can handle unencapsulated or
> IPv6-in-IPv6 packets. Any other tunnel stacks are handled with
> GSO partial.
>
> Validate that the packet can be offloaded in ndo_features_check.
> Main thing we need to check for is that the header geometry can
> be expressed in the decriptor fields (offsets aren't too large).
>
> Report number of TSO super-packets via the qstat API.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> v3:
> - add missing feature clearing in ndo_features_check
> v2: https://lore.kernel.org/20250214235207.2312352-1-kuba@kernel.org
> - checkpatch -> whitespace
> v1: https://lore.kernel.org/20250213005540.1345735-1-kuba@kernel.org
>
> CC: alexanderduyck@fb.com
> CC: jdamato@fastly.com
> ---
> .../net/ethernet/meta/fbnic/fbnic_netdev.h | 3 +
> drivers/net/ethernet/meta/fbnic/fbnic_txrx.h | 1 +
> .../net/ethernet/meta/fbnic/fbnic_netdev.c | 25 ++-
> drivers/net/ethernet/meta/fbnic/fbnic_txrx.c | 146 +++++++++++++++++-
> 4 files changed, 163 insertions(+), 12 deletions(-)
Scanned through this change a few times and nothing obvious stood
out to me, but I'm not super familiar with this driver (despite
being CC'd :P):
Acked-by: Joe Damato <jdamato@fastly.com>
next prev parent reply other threads:[~2025-02-25 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 17:41 [PATCH net-next v3] eth: fbnic: support TCP segmentation offload Jakub Kicinski
2025-02-25 17:15 ` Joe Damato [this message]
2025-02-26 1:40 ` Jakub Kicinski
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=Z736uO_DiO1fkn53@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).