From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>
Cc: Simon Horman <horms@kernel.org>,
<muhammad.husaini.zulkifli@intel.com>,
<przemyslaw.kitszel@intel.com>, <edumazet@google.com>,
<kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] igc: enable HW VLAN insertion/stripping by default
Date: Thu, 13 Mar 2025 08:49:02 -0700 [thread overview]
Message-ID: <3b83936d-10cf-4e32-a7a7-f16bc50e7e57@intel.com> (raw)
In-Reply-To: <CALjTZvb_=NaNE=DS10G=61WK2xXQO35d2sYOd9L=qJ+TtpeeXg@mail.gmail.com>
On 3/13/2025 2:23 AM, Rui Salvaterra wrote:
> Hi, Tony,
>
> On Wed, 12 Mar 2025 at 21:43, Tony Nguyen <anthony.l.nguyen@intel.com> wrote:
>>
>> Unfortunately, I'm unable check with the original author or those
>> involved at the time. From asking around it sounds like there may have
>> been some initial issues when implementing this; my theory is this was
>> off by default so that it would minimize the affects if additional
>> issues were discovered.
>
> I thought about that possibility, but in the end it didn't seem
> logical to me. If the feature was WIP and/or broken in some way, why
> would the user be allowed to enable it via ethtool, ever since it was
> first implemented, in commit 8d7449630e3450bc0546dc0cb692fbb57d1852c0
> (almost four years ago)?
It would allow users to opt-in and use the feature; if an adverse
problem was later found, it could be easily mitigated by not turning the
feature on. If it were on by default, and a problem found, there would a
larger impact. As you mentioned, since the feature has now been in
existence for many years, it's probably safe to have on by default.
>> I see that you missed Intel Wired LAN (intel-wired-lan@lists.osuosl.org)
>> on the patch. Could you resend with the list included? Also, if you
>> could make it 'PATCH iwl-next' to target the Intel -next tree as that
>> seems the appropriate tree.
>
> Oh. That list is marked as moderated, I (wrongly, for sure) assumed
> there would be restrictions when mailing to it. I'll resend correctly
> soon.
Thank you.
- Tony
prev parent reply other threads:[~2025-03-13 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 11:02 [PATCH] igc: enable HW VLAN insertion/stripping by default Rui Salvaterra
2025-03-11 13:52 ` Simon Horman
2025-03-11 13:59 ` Rui Salvaterra
2025-03-12 21:43 ` Tony Nguyen
2025-03-13 9:23 ` Rui Salvaterra
2025-03-13 15:49 ` Tony Nguyen [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=3b83936d-10cf-4e32-a7a7-f16bc50e7e57@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muhammad.husaini.zulkifli@intel.com \
--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