From: Jakub Kicinski <kuba@kernel.org>
To: Sathesh B Edara <sedara@marvell.com>
Cc: <linux-kernel@vger.kernel.org>, <sburla@marvell.com>,
<vburru@marvell.com>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <hgani@marvell.com>, <andrew@lunn.ch>,
<srasheed@marvell.com>, Andrew Lunn <andrew+netdev@lunn.ch>
Subject: Re: [net-next PATCH v1 1/2 RESEND] octeon_ep: Add support to retrieve hardware channel information
Date: Wed, 24 Sep 2025 18:10:49 -0700 [thread overview]
Message-ID: <20250924181049.1ab2dc56@kernel.org> (raw)
In-Reply-To: <20250923094120.13133-2-sedara@marvell.com>
On Tue, 23 Sep 2025 02:41:18 -0700 Sathesh B Edara wrote:
> + channel->max_rx = CFG_GET_PORTS_MAX_IO_RINGS(oct->conf);
> + channel->max_tx = CFG_GET_PORTS_MAX_IO_RINGS(oct->conf);
> + channel->rx_count = CFG_GET_PORTS_ACTIVE_IO_RINGS(oct->conf);
> + channel->tx_count = CFG_GET_PORTS_ACTIVE_IO_RINGS(oct->conf);
AFAICT you're using one IRQ for both Rx and Tx. The channel is
basically an IRQ. So if you're using one for Rx+Tx you should be
reporting the combined channel counts.
--
pw-bot: cr
next prev parent reply other threads:[~2025-09-25 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 9:41 [net-next PATCH v1 0/2 RESEND] Add support to retrieve hardware channel information Sathesh B Edara
2025-09-23 9:41 ` [net-next PATCH v1 1/2 RESEND] octeon_ep: " Sathesh B Edara
2025-09-24 16:53 ` Simon Horman
2025-09-25 1:10 ` Jakub Kicinski [this message]
2025-09-23 9:41 ` [net-next PATCH v1 2/2 RESEND] octeon_ep_vf: " Sathesh B Edara
2025-09-24 16:53 ` Simon Horman
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=20250924181049.1ab2dc56@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hgani@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.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).