From: Jakub Kicinski <kuba@kernel.org>
To: Rushil Gupta <rushilg@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
pkaligineedi@google.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, willemb@google.com,
hramamurthy@google.com, Shailend Chand <shailend@google.com>,
Ziwei Xiao <ziweixiao@google.com>
Subject: Re: [PATCH net-next] gve: Add retry logic for recoverable adminq errors
Date: Fri, 28 Jun 2024 18:02:06 -0700 [thread overview]
Message-ID: <20240628180206.07c0a1b2@kernel.org> (raw)
In-Reply-To: <20240628204139.458075-1-rushilg@google.com>
On Fri, 28 Jun 2024 20:41:39 +0000 Rushil Gupta wrote:
> An adminq command is retried if it fails with an ETIME error code
> which translates to the deadline exceeded error for the device.
> The create and destroy adminq commands are now managed via a common
> method. This method keeps track of return codes for each queue and retries
> the commands for the queues that failed with ETIME.
> Other adminq commands that do not require queue level granularity are
> simply retried in gve_adminq_execute_cmd.
>
> Signed-off-by: Rushil Gupta <rushilg@google.com>
> Signed-off-by: Jeroen de Borst <jeroendb@google.com>
> Reviewed-by: Shailend Chand <shailend@google.com>
> Reviewed-by: Ziwei Xiao <ziweixiao@google.com>
I told you once already that you're not allowed to repost patches
within 24h. You should also include a change long when you repost.
Since Jeroen is a maintainer of this driver, and you are not listed
in the MAINTAINERS file I don't understand why you're the one sending
this. We can't teach everyone at google the upstream process one by
one so I'd like to request that only the listed maintainers post pure
GVE patches (or the folks who are heavily involved upstream).
> diff --git a/drivers/net/ethernet/google/gve/gve_adminq.c b/drivers/net/ethernet/google/gve/gve_adminq.c
> index c5bbc1b7524e..74c61b90ea45 100644
> --- a/drivers/net/ethernet/google/gve/gve_adminq.c
> +++ b/drivers/net/ethernet/google/gve/gve_adminq.c
> @@ -12,7 +12,7 @@
>
> #define GVE_MAX_ADMINQ_RELEASE_CHECK 500
> #define GVE_ADMINQ_SLEEP_LEN 20
> -#define GVE_MAX_ADMINQ_EVENT_COUNTER_CHECK 100
> +#define GVE_MAX_ADMINQ_EVENT_COUNTER_CHECK 1000
>
> #define GVE_DEVICE_OPTION_ERROR_FMT "%s option error:\n" \
> "Expected: length=%d, feature_mask=%x.\n" \
> @@ -415,14 +415,17 @@ static int gve_adminq_parse_err(struct gve_priv *priv, u32 status)
> /* Flushes all AQ commands currently queued and waits for them to complete.
> * If there are failures, it will return the first error.
> */
> -static int gve_adminq_kick_and_wait(struct gve_priv *priv)
> +static int gve_adminq_kick_and_wait(struct gve_priv *priv, int ret_cnt, int *ret_codes)
> {
> int tail, head;
> - int i;
> + int i, j;
>
> tail = ioread32be(&priv->reg_bar0->adminq_event_counter);
> head = priv->adminq_prod_cnt;
>
> + if ((head - tail) > ret_cnt)
please delete all the pointless parenthesis in + lines of this patch.
--
pw-bot: cr
next prev parent reply other threads:[~2024-06-29 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 20:41 [PATCH net-next] gve: Add retry logic for recoverable adminq errors Rushil Gupta
2024-06-29 1:02 ` Jakub Kicinski [this message]
2024-06-29 17:56 ` Rushil Gupta
2024-07-01 21:25 ` Jakub Kicinski
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=20240628180206.07c0a1b2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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).