From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: Pavan Chebbi <pavan.chebbi@broadcom.com>,
Michael Chan <mchan@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC net-next v2 2/2] tg3: Link queues to NAPIs
Date: Thu, 26 Sep 2024 16:17:03 -0700 [thread overview]
Message-ID: <ZvXrbylj0Qt1ycio@LQ3V64L9R2> (raw)
In-Reply-To: <20240925162048.16208-3-jdamato@fastly.com>
On Wed, Sep 25, 2024 at 04:20:48PM +0000, Joe Damato wrote:
> Link queues to NAPIs using the netdev-genl API so this information is
> queryable.
>
> $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/netdev.yaml \
> --dump queue-get --json='{"ifindex": 2}'
>
> [{'id': 0, 'ifindex': 2, 'type': 'rx'},
> {'id': 1, 'ifindex': 2, 'napi-id': 146, 'type': 'rx'},
> {'id': 2, 'ifindex': 2, 'napi-id': 147, 'type': 'rx'},
> {'id': 3, 'ifindex': 2, 'napi-id': 148, 'type': 'rx'},
> {'id': 0, 'ifindex': 2, 'napi-id': 145, 'type': 'tx'}]
>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> ---
> drivers/net/ethernet/broadcom/tg3.c | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c
> index ddf0bb65c929..f78d7e8c40b2 100644
> --- a/drivers/net/ethernet/broadcom/tg3.c
> +++ b/drivers/net/ethernet/broadcom/tg3.c
> @@ -7395,18 +7395,34 @@ static int tg3_poll(struct napi_struct *napi, int budget)
>
> static void tg3_napi_disable(struct tg3 *tp)
> {
> + struct tg3_napi *tnapi;
> int i;
>
> - for (i = tp->irq_cnt - 1; i >= 0; i--)
> - napi_disable(&tp->napi[i].napi);
> + ASSERT_RTNL();
> + for (i = tp->irq_cnt - 1; i >= 0; i--) {
> + tnapi = &tp->napi[i];
> + if (tnapi->tx_buffers)
> + netif_queue_set_napi(tp->dev, i, NETDEV_QUEUE_TYPE_TX, NULL);
It looks like the ASSERT_RTNL is unnecessary; netif_queue_set_napi
will call it internally, so I'll remove it before sending this to
the list (barring any other feedback).
> static void tg3_napi_enable(struct tg3 *tp)
> {
> + struct tg3_napi *tnapi;
> int i;
>
> - for (i = 0; i < tp->irq_cnt; i++)
> - napi_enable(&tp->napi[i].napi);
> + ASSERT_RTNL();
> + for (i = 0; i < tp->irq_cnt; i++) {
> + tnapi = &tp->napi[i];
> + napi_enable(&tnapi->napi);
> + if (tnapi->tx_buffers)
> + netif_queue_set_napi(tp->dev, i, NETDEV_QUEUE_TYPE_TX, &tnapi->napi);
Same as above.
next prev parent reply other threads:[~2024-09-26 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:20 [RFC net-next v2 0/2] tg3: Link IRQs, NAPIs, and queues Joe Damato
2024-09-25 16:20 ` [RFC net-next v2 1/2] tg3: Link IRQs to NAPI instances Joe Damato
2024-09-27 3:58 ` Pavan Chebbi
2024-09-25 16:20 ` [RFC net-next v2 2/2] tg3: Link queues to NAPIs Joe Damato
2024-09-26 23:17 ` Joe Damato [this message]
2024-09-27 4:03 ` Pavan Chebbi
2024-09-27 16:14 ` Joe Damato
2024-10-02 23:21 ` Joe Damato
2024-10-03 4:26 ` Pavan Chebbi
2024-10-03 19:47 ` Joe Damato
2024-10-04 15:33 ` Pavan Chebbi
2024-10-04 16:39 ` Joe Damato
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=ZvXrbylj0Qt1ycio@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@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