From: David Miller <davem@davemloft.net>
To: dcaratti@redhat.com
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org, fbl@redhat.com,
fw@strlen.de
Subject: Re: [PATCH net-next] net: vlan: add support for tunnel offload
Date: Wed, 07 Nov 2018 22:23:53 -0800 (PST) [thread overview]
Message-ID: <20181107.222353.2042064681834666845.davem@davemloft.net> (raw)
In-Reply-To: <b55216ca2bf962175a3f79c73e08607deb4c6e7d.1541586443.git.dcaratti@redhat.com>
From: Davide Caratti <dcaratti@redhat.com>
Date: Wed, 7 Nov 2018 11:28:18 +0100
> GSO tunneled packets are always segmented in software before they are
> transmitted by a VLAN, even when the lower device can offload tunnel
> encapsulation and VLAN together (i.e., some bits in NETIF_F_GSO_ENCAP_ALL
> mask are set in the lower device 'vlan_features'). If we let VLANs have
> the same tunnel offload capabilities as their lower device, throughput
> can improve significantly when CPU is limited on the transmitter side.
>
> - set NETIF_F_GSO_ENCAP_ALL bits in the VLAN 'hw_features', to ensure
> that 'features' will have those bits zeroed only when the lower device
> has no hardware support for tunnel encapsulation.
> - for the same reason, copy GSO-related bits of 'hw_enc_features' from
> lower device to VLAN, and ensure to update that value when the lower
> device changes its features.
> - set NETIF_F_HW_CSUM bit in the VLAN 'hw_enc_features' if 'real_dev'
> is able to compute checksums at least for a kind of packets, like done
> with commit 8403debeead8 ("vlan: Keep NETIF_F_HW_CSUM similar to other
> software devices"). This avoids software segmentation due to mismatching
> checksum capabilities between VLAN's 'features' and 'hw_enc_features'.
>
> Reported-by: Flavio Leitner <fbl@redhat.com>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
Applied.
prev parent reply other threads:[~2018-11-08 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 10:28 [PATCH net-next] net: vlan: add support for tunnel offload Davide Caratti
2018-11-08 6:23 ` David Miller [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=20181107.222353.2042064681834666845.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=fbl@redhat.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox