From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: <netdev@vger.kernel.org>
Subject: Re: [RFC] net: remove NETIF_F_GSO_FRAGLIST from NETIF_F_GSO_SOFTWARE
Date: Tue, 20 Aug 2024 15:12:00 +0200 [thread overview]
Message-ID: <78332215-9b8a-4000-9c5d-98e13f664e67@intel.com> (raw)
In-Reply-To: <20240816075915.6245-1-nbd@nbd.name>
From: Felix Fietkau <nbd@nbd.name>
Date: Fri, 16 Aug 2024 09:59:15 +0200
Please use scripts/get_maintainer.pl next time. I remember it was me who
added fraglist to GSO_SOFTWARE, but I'm not Cced =\
> Several drivers set NETIF_F_GSO_SOFTWARE, but mangle fraglist GRO packets
Which ones precisely?
> in a way that they can't be properly segmented anymore.
> In order to properly deal with this, remove fraglist GSO from
> NETIF_F_GSO_SOFTWARE and switch to NETIF_F_GSO_SOFTWARE_ALL (which includes
> fraglist GSO) in places where it's safe to add.
Why isn't bridge changed? It's only a software layer, I don't think it
break fraglist skbs anyhow.
>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> ---
> drivers/net/dummy.c | 2 +-
> drivers/net/loopback.c | 2 +-
> drivers/net/macvlan.c | 2 +-
> include/linux/netdev_features.h | 5 +++--
> net/8021q/vlan.h | 2 +-
> net/8021q/vlan_dev.c | 4 ++--
> net/core/sock.c | 2 +-
> net/mac80211/ieee80211_i.h | 2 +-
> net/openvswitch/vport-internal_dev.c | 2 +-
> 9 files changed, 12 insertions(+), 11 deletions(-)
Thanks,
Olek
prev parent reply other threads:[~2024-08-20 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:59 [RFC] net: remove NETIF_F_GSO_FRAGLIST from NETIF_F_GSO_SOFTWARE Felix Fietkau
2024-08-16 14:13 ` Willem de Bruijn
2024-08-16 15:29 ` Felix Fietkau
2024-08-20 13:12 ` Alexander Lobakin [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=78332215-9b8a-4000-9c5d-98e13f664e67@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=nbd@nbd.name \
--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