From: Jakub Kicinski <kuba@kernel.org>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Michael Chan <michael.chan@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] Applicability of using 'txq_trans_update' during ring recovery
Date: Tue, 12 Apr 2022 14:49:06 -0700 [thread overview]
Message-ID: <20220412144906.40d935f2@kernel.org> (raw)
In-Reply-To: <040cd578-946f-0141-c28a-2f04d00d9790@broadcom.com>
On Tue, 12 Apr 2022 12:34:23 -0700 Ray Jui wrote:
> Sure, that is the general error recovery case which is very different
> from this specific recovery case we are discussing here. This specific
> recovery is solely performed by driver (without resetting firmware and
> chip) on a per NAPI ring set basis. While a specific NAPI ring set is
> being recovered, traffic is still going with the rest of the NAPI ring
> sets. Average recovery time is in the 1 - 2 ms range in this type of
> recovery.
>
> Also as I already said, 'netif_carrier_off' is not an option given that
> the RoCE/infiniband subsystem has a dependency on 'netif_carrier_status'
> for many of their operations.
>
> Basically I'm looking for a solution that allows one to be able to:
> 1) quieice traffic and perform recovery on a per NAPI ring set basis
> 2) During recovery, it does not cause any drastic effect on RoCE
>
> 'txq_trans_update' may not be the most optimal solution, but it is a
> solution that satisfies the two requirements above. If there are any
> other option that is considered more optimal than 'txq_trans_update' and
> can satisfy the two requirements, please let me know.
The optimal solution would be to not have to reset your rings and
pretend like nothing happened :/ If you can't reset the ring in time
you'll have to live with the splat. End of story.
next prev parent reply other threads:[~2022-04-12 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 17:01 [RFC] Applicability of using 'txq_trans_update' during ring recovery Ray Jui
2022-04-12 17:37 ` Jakub Kicinski
2022-04-12 18:08 ` Ray Jui
2022-04-12 18:24 ` Michael Chan
2022-04-12 18:36 ` Ray Jui
2022-04-12 19:19 ` Michael Chan
2022-04-12 19:34 ` Ray Jui
2022-04-12 21:49 ` Jakub Kicinski [this message]
2022-04-12 22:21 ` Ray Jui
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=20220412144906.40d935f2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ray.jui@broadcom.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).