From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Faizal Rahim <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>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
Subject: Re: [PATCH net 1/1] igc: Fix double reset adapter triggered from a single taprio cmd
Date: Wed, 26 Jun 2024 15:29:47 -0700 [thread overview]
Message-ID: <87ed8j72xw.fsf@intel.com> (raw)
In-Reply-To: <20240625082656.2702440-1-faizal.abdul.rahim@linux.intel.com>
Faizal Rahim <faizal.abdul.rahim@linux.intel.com> writes:
> Following the implementation of "igc: Add TransmissionOverrun counter"
> patch, when a taprio command is triggered by user, igc processes two
> commands: TAPRIO_CMD_REPLACE followed by TAPRIO_CMD_STATS. However, both
> commands unconditionally pass through igc_tsn_offload_apply() which
> evaluates and triggers reset adapter. The double reset causes issues in
> the calculation of adapter->qbv_count in igc.
>
> TAPRIO_CMD_REPLACE command is expected to reset the adapter since it
> activates qbv. It's unexpected for TAPRIO_CMD_STATS to do the same
> because it doesn't configure any driver-specific TSN settings. So, the
> evaluation in igc_tsn_offload_apply() isn't needed for TAPRIO_CMD_STATS.
>
> To address this, commands parsing are relocated to
> igc_tsn_enable_qbv_scheduling(). Commands that don't require an adapter
> reset will exit after processing, thus avoiding igc_tsn_offload_apply().
>
> Fixes: d3750076d464 ("igc: Add TransmissionOverrun counter")
> Signed-off-by: Faizal Rahim <faizal.abdul.rahim@linux.intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc_main.c | 33 ++++++++++++-----------
> 1 file changed, 17 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/igc/igc_main.c b/drivers/net/ethernet/intel/igc/igc_main.c
> index 87b655b839c1..33069880c86c 100644
> --- a/drivers/net/ethernet/intel/igc/igc_main.c
> +++ b/drivers/net/ethernet/intel/igc/igc_main.c
> @@ -6310,21 +6310,6 @@ static int igc_save_qbv_schedule(struct igc_adapter *adapter,
> size_t n;
> int i;
>
> - switch (qopt->cmd) {
> - case TAPRIO_CMD_REPLACE:
> - break;
> - case TAPRIO_CMD_DESTROY:
> - return igc_tsn_clear_schedule(adapter);
> - case TAPRIO_CMD_STATS:
> - igc_taprio_stats(adapter->netdev, &qopt->stats);
> - return 0;
> - case TAPRIO_CMD_QUEUE_STATS:
> - igc_taprio_queue_stats(adapter->netdev, &qopt->queue_stats);
> - return 0;
> - default:
> - return -EOPNOTSUPP;
> - }
> -
> if (qopt->base_time < 0)
> return -ERANGE;
>
> @@ -6433,7 +6418,23 @@ static int igc_tsn_enable_qbv_scheduling(struct igc_adapter *adapter,
> if (hw->mac.type != igc_i225)
> return -EOPNOTSUPP;
>
> - err = igc_save_qbv_schedule(adapter, qopt);
> + switch (qopt->cmd) {
> + case TAPRIO_CMD_REPLACE:
> + err = igc_save_qbv_schedule(adapter, qopt);
> + break;
> + case TAPRIO_CMD_DESTROY:
> + err = igc_tsn_clear_schedule(adapter);
> + break;
> + case TAPRIO_CMD_STATS:
> + igc_taprio_stats(adapter->netdev, &qopt->stats);
> + return 0;
> + case TAPRIO_CMD_QUEUE_STATS:
> + igc_taprio_queue_stats(adapter->netdev, &qopt->queue_stats);
> + return 0;
> + default:
> + return -EOPNOTSUPP;
> + }
> +
Yeah, moving the command parsing to be done earlier sounds like the
right fix:
Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> if (err)
> return err;
>
> --
> 2.25.1
>
--
Vinicius
next prev parent reply other threads:[~2024-06-26 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 8:26 [PATCH net 1/1] igc: Fix double reset adapter triggered from a single taprio cmd Faizal Rahim
2024-06-26 1:19 ` Abdul Rahim, Faizal
2024-06-27 22:46 ` Vladimir Oltean
2024-06-26 22:29 ` Vinicius Costa Gomes [this message]
2024-07-23 7:33 ` [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=87ed8j72xw.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=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=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).