From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Paul Barker <paul.barker.ct@bp.renesas.com>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] net: ravb: Always process TX descriptor ring
Date: Tue, 26 Mar 2024 10:38:43 +0100 [thread overview]
Message-ID: <20240326093843.GD1108818@ragnatech.se> (raw)
In-Reply-To: <20240326083740.23364-1-paul.barker.ct@bp.renesas.com>
Hi Paul,
Thanks for your work.
On 2024-03-26 08:37:39 +0000, Paul Barker wrote:
> The TX queue should be serviced each time the poll function is called,
> even if the full RX work budget has been consumed. This prevents
> starvation of the TX queue when RX bandwidth usage is high.
Is this not a design decision? That the driver should prioritize Rx over
Tx if there is contention. I have no opinion on if this design is good
or bad, I let Sergey judge that.
>
> Fixes: a0d2f20650e8 ("Renesas Ethernet AVB PTP clock driver")
However, I do not think it is a bug and should not have a fixes tag.
Also this fixes tag is incorrect, this points to the commit where ravb.c
was renamed ravb_main.c. ravb_poll() is not touched by this commit.
> Signed-off-by: Paul Barker <paul.barker.ct@bp.renesas.com>
> ---
> drivers/net/ethernet/renesas/ravb_main.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c
> index d1be030c8848..4f98e4e2badb 100644
> --- a/drivers/net/ethernet/renesas/ravb_main.c
> +++ b/drivers/net/ethernet/renesas/ravb_main.c
> @@ -1324,12 +1324,12 @@ static int ravb_poll(struct napi_struct *napi, int budget)
> int q = napi - priv->napi;
> int mask = BIT(q);
> int quota = budget;
> + bool rearm = true;
>
> /* Processing RX Descriptor Ring */
> /* Clear RX interrupt */
> ravb_write(ndev, ~(mask | RIS0_RESERVED), RIS0);
> - if (ravb_rx(ndev, "a, q))
> - goto out;
> + rearm = !ravb_rx(ndev, "a, q);
>
> /* Processing TX Descriptor Ring */
> spin_lock_irqsave(&priv->lock, flags);
> @@ -1339,6 +1339,9 @@ static int ravb_poll(struct napi_struct *napi, int budget)
> netif_wake_subqueue(ndev, q);
> spin_unlock_irqrestore(&priv->lock, flags);
>
> + if (!rearm)
> + goto out;
> +
> napi_complete(napi);
>
> /* Re-enable RX/TX interrupts */
>
> base-commit: 4cece764965020c22cff7665b18a012006359095
> --
> 2.44.0
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-03-26 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 8:37 [PATCH 1/2] net: ravb: Always process TX descriptor ring Paul Barker
2024-03-26 8:37 ` [PATCH 2/2] net: ravb: Always update error counters Paul Barker
2024-03-26 9:42 ` Niklas Söderlund
2024-03-26 20:45 ` Sergey Shtylyov
2024-03-26 9:38 ` Niklas Söderlund [this message]
2024-03-26 9:54 ` [PATCH 1/2] net: ravb: Always process TX descriptor ring Paul Barker
2024-03-26 13:09 ` Niklas Söderlund
2024-03-27 20:59 ` Sergey Shtylyov
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=20240326093843.GD1108818@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
/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).