From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: "Abdul Rahim, Faizal" <faizal.abdul.rahim@linux.intel.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Simon Horman <horms@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Sasha Neftin <sasha.neftin@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH iwl-net v2 2/3] igc: Fix reset adapter logics when tx mode change
Date: Thu, 11 Jul 2024 11:10:11 -0700 [thread overview]
Message-ID: <87le27ssu4.fsf@intel.com> (raw)
In-Reply-To: <6bb1ba4a-41ba-4bc1-9c4b-abfb27944891@linux.intel.com>
"Abdul Rahim, Faizal" <faizal.abdul.rahim@linux.intel.com> writes:
> Hi Vinicius,
>
> On 11/7/2024 6:44 am, Vinicius Costa Gomes wrote:
>> Faizal Rahim <faizal.abdul.rahim@linux.intel.com> writes:
>>
>>> Following the "igc: Fix TX Hang issue when QBV Gate is close" changes,
>>> remaining issues with the reset adapter logic in igc_tsn_offload_apply()
>>> have been observed:
>>>
>>> 1. The reset adapter logics for i225 and i226 differ, although they should
>>> be the same according to the guidelines in I225/6 HW Design Section
>>> 7.5.2.1 on software initialization during tx mode changes.
>>> 2. The i225 resets adapter every time, even though tx mode doesn't change.
>>> This occurs solely based on the condition igc_is_device_id_i225() when
>>> calling schedule_work().
>>> 3. i226 doesn't reset adapter for tsn->legacy tx mode changes. It only
>>> resets adapter for legacy->tsn tx mode transitions.
>>> 4. qbv_count introduced in the patch is actually not needed; in this
>>> context, a non-zero value of qbv_count is used to indicate if tx mode
>>> was unconditionally set to tsn in igc_tsn_enable_offload(). This could
>>> be replaced by checking the existing register
>>> IGC_TQAVCTRL_TRANSMIT_MODE_TSN bit.
>>>
>>> This patch resolves all issues and enters schedule_work() to reset the
>>> adapter only when changing tx mode. It also removes reliance on qbv_count.
>>>
>>> qbv_count field will be removed in a future patch.
>>>
>>> Test ran:
>>>
>>> 1. Verify reset adapter behaviour in i225/6:
>>> a) Enrol a new GCL
>>> Reset adapter observed (tx mode change legacy->tsn)
>>> b) Enrol a new GCL without deleting qdisc
>>> No reset adapter observed (tx mode remain tsn->tsn)
>>> c) Delete qdisc
>>> Reset adapter observed (tx mode change tsn->legacy)
>>>
>>> 2. Tested scenario from "igc: Fix TX Hang issue when QBV Gate is closed"
>>> to confirm it remains resolved.
>>>
>>> Fixes: 175c241288c0 ("igc: Fix TX Hang issue when QBV Gate is closed")
>>> Signed-off-by: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
>>> Reviewed-by: Simon Horman <horms@kernel.org>
>>> ---
>>
>> There were a quite a few bugs, some of them my fault, on this part of
>> the code, changing between the modes in the hardware.
>>
>> So I would like some confirmation that ETF offloading/LaunchTime was
>> also tested with this change. Just to be sure.
>>
>> But code-wise, looks good:
>>
>> Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>>
>>
>> Cheers,
>
>
> Tested etf with offload, looks like working correctly.
>
> 1. mqprio
> tc qdisc add dev enp1s0 handle 100: parent root mqprio num_tc 3 \
> map 2 2 1 0 2 2 2 2 2 2 2 2 2 2 2 2 \
> queues 1@0 1@1 2@2 \
> hw 0
>
> No reset adapter observed.
>
> 2. etf with offload
> tc qdisc replace dev enp1s0 parent 100:1 etf \
> clockid CLOCK_TAI delta 300000 offload
>
> Reset adapter observed (tx mode legacy -> tsn).
>
> 3. delete qdisc
> tc qdisc delete dev enp1s0 parent root handle 100
>
> Reset adapter observed (tx mode tsn -> legacy).
>
That no unexpected resets are happening, is good.
But what I had in mind was some functional tests that ETF is working. I
guess that's the only way of knowing that it's still working. Sorry that
I wasn't clear about that.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2024-07-11 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 12:53 [PATCH iwl-net v2 0/3] igc bug fixes related to qbv_count usage Faizal Rahim
2024-07-07 12:53 ` [PATCH iwl-net v2 1/3] igc: Fix qbv_config_change_errors logics Faizal Rahim
2024-07-07 12:57 ` [Intel-wired-lan] " kernel test robot
2024-07-10 23:46 ` Vinicius Costa Gomes
2024-08-01 7:32 ` [Intel-wired-lan] " Mor Bar-Gabay
2024-07-07 12:53 ` [PATCH iwl-net v2 2/3] igc: Fix reset adapter logics when tx mode change Faizal Rahim
2024-07-10 23:44 ` Vinicius Costa Gomes
2024-07-11 11:50 ` Abdul Rahim, Faizal
2024-07-11 18:10 ` Vinicius Costa Gomes [this message]
2024-07-17 7:02 ` Abdul Rahim, Faizal
2024-07-17 22:03 ` Vinicius Costa Gomes
2024-07-22 8:25 ` [Intel-wired-lan] " Rodrigo CADORE CATALDO
2024-08-01 7:36 ` Mor Bar-Gabay
2024-07-07 12:53 ` [PATCH iwl-net v2 3/3] igc: Fix qbv tx latency by setting gtxoffset Faizal Rahim
2024-07-10 23:48 ` Vinicius Costa Gomes
2024-08-01 7:37 ` [Intel-wired-lan] " Mor Bar-Gabay
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=87le27ssu4.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=richardcochran@gmail.com \
--cc=sasha.neftin@intel.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).