[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240530173902.7f00a610@kernel.org>
Date: Thu, 30 May 2024 17:39:02 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>, Saeed Mahameed <saeedm@...dia.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
nalramli@...tly.com, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Leon Romanovsky <leon@...nel.org>, "open
list:MELLANOX MLX5 core VPI driver" <linux-rdma@...r.kernel.org>, Paolo
Abeni <pabeni@...hat.com>, Richard Cochran <richardcochran@...il.com>,
Tariq Toukan <tariqt@...dia.com>
Subject: Re: [RFC net-next v3 0/2] mlx5: Add netdev-genl queue stats
On Thu, 30 May 2024 17:15:25 -0700 Joe Damato wrote:
> > Why to base, and not report them as queue stats?
> >
> > Judging by mlx5e_update_tx_netdev_queues() calls sprinkled in
> > ../mlx5/core/en/htb.c it seems that the driver will update the
> > real_num_tx_queues accordingly. And from mlx5e_qid_from_qos()
> > it seems like the inverse calculation is:
> >
> > i - (chs->params.num_channels + is_ptp)*mlx5e_get_dcb_num_tc(&chs->params)
> >
> > But really, isn't it enough to use priv->txq2sq[i] for the active
> > queues, and not active ones you've already covered?
>
> This is what I proposed in the thread for the v2, but Tariq
> suggested a different approach he liked more, please see this
> message for more details:
>
> https://lore.kernel.org/netdev/68225941-f3c3-4335-8f3d-edee43f59033@gmail.com/
>
> I attempted to implement option 1 as he described in his message.
I see, although it sounds like option 2 would also work.
Saeed can you shine any light here? I'm worried Tariq is already AFK
for the weekend and we'll make no progress until Monday...
Powered by blists - more mailing lists