From: Brett Creeley <bcreeley@amd.com>
To: Roger Quadros <rogerq@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Julien Panis <jpanis@baylibre.com>
Cc: Simon Horman <horms@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
srk@ti.com, vigneshr@ti.com, danishanwar@ti.com,
pekka Varis <p-varis@ti.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/6] net: ethernet: ti: am65-cpsw: Introduce multi queue Rx
Date: Tue, 23 Jul 2024 14:10:18 -0700 [thread overview]
Message-ID: <2a1b2099-e1c4-4d04-bc97-9ff7e0621275@amd.com> (raw)
In-Reply-To: <20240703-am65-cpsw-multi-rx-v3-1-f11cd860fd72@kernel.org>
On 7/3/2024 6:51 AM, Roger Quadros wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> am65-cpsw can support up to 8 queues at Rx.
> Use a macro AM65_CPSW_MAX_RX_QUEUES to indicate that.
> As there is only one DMA channel for RX traffic, the
> 8 queues come as 8 flows in that channel.
>
> By default, we will start with 1 flow as defined by the
> macro AM65_CPSW_DEFAULT_RX_CHN_FLOWS.
>
> User can change the number of flows by ethtool like so
> 'ethtool -L ethx rx <N>'
>
> All traffic will still come on flow 0. To get traffic on
> different flows the Classifiers will need to be set up.
>
> Signed-off-by: Roger Quadros <rogerq@kernel.org>
> Reviewed-by: Simon Horman <horms@kernel.org>
> ---
> Changelog:
> v3:
> - style fixes: reverse xmas tree and checkpatch.pl --max-line-length=80
> - typo fix: Classifer -> Classifier
> - added Reviewed-by Simon Horman
> ---
> drivers/net/ethernet/ti/am65-cpsw-ethtool.c | 62 +++--
> drivers/net/ethernet/ti/am65-cpsw-nuss.c | 367 ++++++++++++++++------------
> drivers/net/ethernet/ti/am65-cpsw-nuss.h | 36 +--
> 3 files changed, 284 insertions(+), 181 deletions(-)
>
> diff --git a/drivers/net/ethernet/ti/am65-cpsw-ethtool.c b/drivers/net/ethernet/ti/am65-cpsw-ethtool.c
> index a1d0935d1ebe..01e3967852e0 100644
> --- a/drivers/net/ethernet/ti/am65-cpsw-ethtool.c
> +++ b/drivers/net/ethernet/ti/am65-cpsw-ethtool.c
> @@ -429,7 +429,7 @@ static void am65_cpsw_get_channels(struct net_device *ndev,
>
> ch->max_rx = AM65_CPSW_MAX_RX_QUEUES;
> ch->max_tx = AM65_CPSW_MAX_TX_QUEUES;
> - ch->rx_count = AM65_CPSW_MAX_RX_QUEUES;
> + ch->rx_count = common->rx_ch_num_flows;
> ch->tx_count = common->tx_ch_num;
> }
>
> @@ -448,8 +448,10 @@ static int am65_cpsw_set_channels(struct net_device *ndev,
> return -EBUSY;
>
> am65_cpsw_nuss_remove_tx_chns(common);
> + am65_cpsw_nuss_remove_rx_chns(common);
>
> - return am65_cpsw_nuss_update_tx_chns(common, chs->tx_count);
> + return am65_cpsw_nuss_update_tx_rx_chns(common, chs->tx_count,
> + chs->rx_count);
> }
>
> static void
> @@ -920,11 +922,13 @@ static int am65_cpsw_get_coalesce(struct net_device *ndev, struct ethtool_coales
> struct netlink_ext_ack *extack)
> {
> struct am65_cpsw_common *common = am65_ndev_to_common(ndev);
> + struct am65_cpsw_rx_flow *rx_flow;
> struct am65_cpsw_tx_chn *tx_chn;
>
> tx_chn = &common->tx_chns[0];
> + rx_flow = &common->rx_chns.flows[0];
>
> - coal->rx_coalesce_usecs = common->rx_pace_timeout / 1000;
> + coal->rx_coalesce_usecs = rx_flow->rx_pace_timeout / 1000;
> coal->tx_coalesce_usecs = tx_chn->tx_pace_timeout / 1000;
>
> return 0;
> @@ -934,14 +938,26 @@ static int am65_cpsw_get_per_queue_coalesce(struct net_device *ndev, u32 queue,
> struct ethtool_coalesce *coal)
> {
> struct am65_cpsw_common *common = am65_ndev_to_common(ndev);
> + struct am65_cpsw_rx_flow *rx_flow;
> struct am65_cpsw_tx_chn *tx_chn;
>
> - if (queue >= AM65_CPSW_MAX_TX_QUEUES)
> + if (queue >= AM65_CPSW_MAX_TX_QUEUES &&
> + queue >= AM65_CPSW_MAX_RX_QUEUES)
> return -EINVAL;
>
> - tx_chn = &common->tx_chns[queue];
> + if (queue < AM65_CPSW_MAX_TX_QUEUES) {
> + tx_chn = &common->tx_chns[queue];
> + coal->tx_coalesce_usecs = tx_chn->tx_pace_timeout / 1000;
> + } else {
> + coal->tx_coalesce_usecs = ~0;
> + }
>
> - coal->tx_coalesce_usecs = tx_chn->tx_pace_timeout / 1000;
> + if (queue < AM65_CPSW_MAX_RX_QUEUES) {
> + rx_flow = &common->rx_chns.flows[queue];
> + coal->rx_coalesce_usecs = rx_flow->rx_pace_timeout / 1000;
> + } else {
> + coal->rx_coalesce_usecs = ~0;
> + }
Minor nit, but after removing the dead code below the check for queue
being greater than max values, I think am65_cpsw_get_coalesce() and
am65_get_per_queue_coalesce() are identical except the "u32 queue" argument.
I think you could do something like the following:
static int am65_cpsw_get_per_queue_coalesce(struct net_device *ndev,
struct ethtool_coalesce *coal,
struct netlink_ext_ack *extack)
{
return __am65_cpsw_get_coalesce(ndev, coal, 0);
}
static int am65_cpsw_get_coalesce(struct net_device *ndev, u32 queue,
struct ethtool_coalesce *coal,
struct netlink_ext_ack *extack,
u32 )
{
return __am65_cpsw_get_coalesce(ndev, coal, queue);
}
>
> return 0;
> }
> @@ -951,9 +967,11 @@ static int am65_cpsw_set_coalesce(struct net_device *ndev, struct ethtool_coales
> struct netlink_ext_ack *extack)
> {
> struct am65_cpsw_common *common = am65_ndev_to_common(ndev);
> + struct am65_cpsw_rx_flow *rx_flow;
> struct am65_cpsw_tx_chn *tx_chn;
>
> tx_chn = &common->tx_chns[0];
> + rx_flow = &common->rx_chns.flows[0];
>
> if (coal->rx_coalesce_usecs && coal->rx_coalesce_usecs < 20)
> return -EINVAL;
> @@ -961,7 +979,7 @@ static int am65_cpsw_set_coalesce(struct net_device *ndev, struct ethtool_coales
> if (coal->tx_coalesce_usecs && coal->tx_coalesce_usecs < 20)
> return -EINVAL;
Why does this return -EINVAL here, but
am65_cpsw_set_per_queue_coalesce() prints a dev_info() and then set the
value to 20?
Would it better to have consistent behavior? Maybe I'm missing some
context or reasoning here?
>
> - common->rx_pace_timeout = coal->rx_coalesce_usecs * 1000;
> + rx_flow->rx_pace_timeout = coal->rx_coalesce_usecs * 1000;
> tx_chn->tx_pace_timeout = coal->tx_coalesce_usecs * 1000;
>
> return 0;
> @@ -971,20 +989,36 @@ static int am65_cpsw_set_per_queue_coalesce(struct net_device *ndev, u32 queue,
> struct ethtool_coalesce *coal)
> {
> struct am65_cpsw_common *common = am65_ndev_to_common(ndev);
> + struct am65_cpsw_rx_flow *rx_flow;
> struct am65_cpsw_tx_chn *tx_chn;
>
> - if (queue >= AM65_CPSW_MAX_TX_QUEUES)
> + if (queue >= AM65_CPSW_MAX_TX_QUEUES &&
> + queue >= AM65_CPSW_MAX_RX_QUEUES)
> return -EINVAL;
>
> - tx_chn = &common->tx_chns[queue];
> + if (queue < AM65_CPSW_MAX_TX_QUEUES) {
> + tx_chn = &common->tx_chns[queue];
> +
> + if (coal->tx_coalesce_usecs && coal->tx_coalesce_usecs < 20) {
> + dev_info(common->dev, "defaulting to min value of 20us for tx-usecs for tx-%u\n",
> + queue);
> + coal->tx_coalesce_usecs = 20;
> + }
>
> - if (coal->tx_coalesce_usecs && coal->tx_coalesce_usecs < 20) {
> - dev_info(common->dev, "defaulting to min value of 20us for tx-usecs for tx-%u\n",
> - queue);
> - coal->tx_coalesce_usecs = 20;
> + tx_chn->tx_pace_timeout = coal->tx_coalesce_usecs * 1000;
> }
>
> - tx_chn->tx_pace_timeout = coal->tx_coalesce_usecs * 1000;
> + if (queue < AM65_CPSW_MAX_RX_QUEUES) {
> + rx_flow = &common->rx_chns.flows[queue];
> +
> + if (coal->rx_coalesce_usecs && coal->rx_coalesce_usecs < 20) {
> + dev_info(common->dev, "defaulting to min value of 20us for rx-usecs for rx-%u\n",
> + queue);
Would it make more sense to just return -EINVAL here similar to the
standard "set_coalesce"?
> + coal->rx_coalesce_usecs = 20;
> + }
> +
> + rx_flow->rx_pace_timeout = coal->rx_coalesce_usecs * 1000;
> + }
>
> return 0;
> }
I think my comment to the "get" and "get_per_queue" versions of these
functions also applies here, but only if the behavior of returning
-EINVAL or setting a value for the user is the same between the "set"
and "set_per_queue".
Thanks,
Brett
<snip>
next prev parent reply other threads:[~2024-07-23 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 13:51 [PATCH net-next v3 0/6] net: ethernet: ti: am65-cpsw: Add multi queue RX support Roger Quadros
2024-07-03 13:51 ` [PATCH net-next v3 1/6] net: ethernet: ti: am65-cpsw: Introduce multi queue Rx Roger Quadros
2024-07-06 1:15 ` Jakub Kicinski
2024-07-08 19:42 ` Roger Quadros
2024-07-23 17:11 ` Joe Damato
2024-07-27 6:29 ` Roger Quadros
2024-09-09 14:17 ` Roger Quadros
2024-07-23 21:10 ` Brett Creeley [this message]
2024-07-27 6:27 ` Roger Quadros
2024-07-03 13:51 ` [PATCH net-next v3 2/6] net: ethernet: ti: cpsw_ale: use regfields for ALE registers Roger Quadros
2024-07-03 13:51 ` [PATCH net-next v3 3/6] net: ethernet: ti: cpsw_ale: use regfields for number of Entries and Policers Roger Quadros
2024-07-03 13:51 ` [PATCH net-next v3 4/6] net: ethernet: ti: cpsw_ale: add Policer and Thread control register fields Roger Quadros
2024-07-03 13:51 ` [PATCH net-next v3 5/6] net: ethernet: ti: cpsw_ale: add policer/classifier helpers and setup defaults Roger Quadros
2024-07-04 8:54 ` Simon Horman
2024-07-03 13:51 ` [PATCH net-next v3 6/6] net: ethernet: ti: am65-cpsw: setup priority to flow mapping Roger Quadros
2024-07-04 9:59 ` [PATCH net-next v3 0/6] net: ethernet: ti: am65-cpsw: Add multi queue RX support MD Danish Anwar
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=2a1b2099-e1c4-4d04-bc97-9ff7e0621275@amd.com \
--to=bcreeley@amd.com \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jpanis@baylibre.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p-varis@ti.com \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.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