From: "Abdul Rahim, Faizal" <faizal.abdul.rahim@linux.intel.com>
To: Kurt Kanzenbach <kurt@linutronix.de>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next] igc: Change Tx mode for MQPRIO offloading
Date: Fri, 21 Feb 2025 17:39:06 +0800 [thread overview]
Message-ID: <d831ac5e-96b9-47de-93ed-3d4f10a8b2aa@linux.intel.com> (raw)
In-Reply-To: <87wmdj8ydu.fsf@kurt.kurt.home>
>>> diff --git a/drivers/net/ethernet/intel/igc/igc_tsn.c b/drivers/net/ethernet/intel/igc/igc_tsn.c
>>> index 1e44374ca1ffbb86e9893266c590f318984ef574..6e4582de9602db2c6667f1736cc2acaa4d4b5201 100644
>>> --- a/drivers/net/ethernet/intel/igc/igc_tsn.c
>>> +++ b/drivers/net/ethernet/intel/igc/igc_tsn.c
>>> @@ -47,7 +47,7 @@ static unsigned int igc_tsn_new_flags(struct igc_adapter *adapter)
>>> new_flags |= IGC_FLAG_TSN_QAV_ENABLED;
>>>
>>> if (adapter->strict_priority_enable)
>>> - new_flags |= IGC_FLAG_TSN_LEGACY_ENABLED;
>>> + new_flags |= IGC_FLAG_TSN_QBV_ENABLED;
>>>
>>> return new_flags;
>>> }
>>
>> IGC_FLAG_TSN_QBV_ENABLED is set multiple times in different lines:
>>
>> if (adapter->taprio_offload_enable)
>> new_flags |= IGC_FLAG_TSN_QBV_ENABLED;
>>
>> if (is_any_launchtime(adapter))
>> new_flags |= IGC_FLAG_TSN_QBV_ENABLED;
>>
>> if (is_cbs_enabled(adapter))
>> new_flags |= IGC_FLAG_TSN_QAV_ENABLED;
>>
>> if (adapter->strict_priority_enable)
>> new_flags |= IGC_FLAG_TSN_QBV_ENABLED;
>>
>> return new_flags;
>> }
>>
>> We can combine the conditions to simplify:
>> if (adapter->taprio_offload_enable ||
>> is_any_launchtime(adapter) ||
>> adapter->strict_priority_enable)
>> new_flags |= IGC_FLAG_TSN_QBV_ENABLED;
>
> Sure.
>
> Should I send a v2 or do you want to carry this patch in your next fpe
> series?
I think you can go ahead with v2. It shouldn’t conflict much with the next
fpe series, and if my future series gets stalled, at least yours won’t be
affected.
prev parent reply other threads:[~2025-02-21 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:45 [PATCH iwl-next] igc: Change Tx mode for MQPRIO offloading Kurt Kanzenbach
2025-02-21 7:23 ` Abdul Rahim, Faizal
2025-02-21 9:01 ` Kurt Kanzenbach
2025-02-21 9:39 ` Abdul Rahim, Faizal [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=d831ac5e-96b9-47de-93ed-3d4f10a8b2aa@linux.intel.com \
--to=faizal.abdul.rahim@linux.intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).