From: Joe Damato <jdamato@fastly.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: netdev@vger.kernel.org, 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: [net-next v3 2/2] tg3: Link queues to NAPIs
Date: Mon, 7 Oct 2024 10:23:40 -0400 [thread overview]
Message-ID: <ZwPu7DmYwwK_uDmD@LQ3V64L9R2> (raw)
In-Reply-To: <CACKFLiknyPntcYXrhsVkz5Mpt9kep0cnkYBGVb1f74x5+HS4Cg@mail.gmail.com>
On Mon, Oct 07, 2024 at 12:30:09AM -0700, Michael Chan wrote:
> On Sat, Oct 5, 2024 at 7:57 AM Joe Damato <jdamato@fastly.com> wrote:
> > + if (tnapi->tx_buffers) {
> > + netif_queue_set_napi(tp->dev, txq_idx,
> > + NETDEV_QUEUE_TYPE_TX,
> > + &tnapi->napi);
> > + txq_idx++;
> > + } else if (tnapi->rx_rcb) {
>
> Shouldn't this be "if" instead of "else if" ? A napi can be for both
> a TX ring and an RX ring in some cases.
> Thanks.
BTW: tg3 set_channels doesn't seem to support combined queues;
combined_count is not even examined in set_channels. But maybe
the link queue can be a combined queue, I don't know.
Regardless, I'll still make the change you requested as there is
similar code in tg3_request_irq.
But what I really would like to get feedback on is the rxq and txq
indexing with the running counters, please. That was called out
explicitly in the cover letter.
Thanks.
next prev parent reply other threads:[~2024-10-07 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 14:57 [RFC net-next v2 0/2] tg3: Link IRQs, NAPIs, and queues Joe Damato
2024-10-05 14:57 ` [net-next v3 1/2] tg3: Link IRQs to NAPI instances Joe Damato
2024-10-05 14:57 ` [net-next v3 2/2] tg3: Link queues to NAPIs Joe Damato
2024-10-07 7:30 ` Michael Chan
2024-10-07 13:38 ` Joe Damato
2024-10-07 14:23 ` Joe Damato [this message]
2024-10-07 22:39 ` Michael Chan
2024-10-06 21:15 ` [RFC net-next v2 0/2] tg3: Link IRQs, NAPIs, and queues 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=ZwPu7DmYwwK_uDmD@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=michael.chan@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