From: Kurt Kanzenbach <kurt@linutronix.de>
To: Rui Salvaterra <rsalvaterra@gmail.com>,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com
Cc: edumazet@google.com, kuba@kernel.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rui Salvaterra <rsalvaterra@gmail.com>
Subject: Re: [PATCH iwl-next] igc: enable HW vlan tag insertion/stripping by default
Date: Wed, 19 Mar 2025 11:19:41 +0100 [thread overview]
Message-ID: <87sen9qq4i.fsf@kurt.kurt.home> (raw)
In-Reply-To: <20250313093615.8037-1-rsalvaterra@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Thu Mar 13 2025, Rui Salvaterra wrote:
> This is enabled by default in other Intel drivers I've checked (e1000, e1000e,
> iavf, igb and ice). Fixes an out-of-the-box performance issue when running
> OpenWrt on typical mini-PCs with igc-supported Ethernet controllers and 802.1Q
> VLAN configurations, as ethtool isn't part of the default packages and sane
> defaults are expected.
>
> In my specific case, with an Intel N100-based machine with four I226-V Ethernet
> controllers, my upload performance increased from under 30 Mb/s to the expected
> ~1 Gb/s.
>
> Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
Great, thanks a lot.
Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-03-19 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 9:35 [PATCH iwl-next] igc: enable HW vlan tag insertion/stripping by default Rui Salvaterra
2025-03-18 14:48 ` Simon Horman
2025-03-18 15:14 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-03-19 10:19 ` Kurt Kanzenbach [this message]
2025-03-27 12:53 ` Mor Bar-Gabay
2025-03-28 15:01 ` Rui Salvaterra
2025-03-28 15:51 ` Tony Nguyen
2025-03-28 16:17 ` Rui Salvaterra
2025-04-01 21:22 ` Tony Nguyen
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=87sen9qq4i.fsf@kurt.kurt.home \
--to=kurt@linutronix.de \
--cc=anthony.l.nguyen@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=rsalvaterra@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;
as well as URLs for NNTP newsgroup(s).