From: Saeed Mahameed <saeedm@mellanox.com>
To: "dsahern@gmail.com" <dsahern@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: max channels for mlx5
Date: Mon, 4 May 2020 21:46:13 +0000 [thread overview]
Message-ID: <2f5110e579a21737e5c13b23482eff6fdb6f3808.camel@mellanox.com> (raw)
In-Reply-To: <198081c2-cb0d-e1d5-901c-446b63c36706@gmail.com>
On Sun, 2020-05-03 at 18:41 -0600, David Ahern wrote:
> Hi Saeed:
>
> When I saw this commit last year:
>
> commit 57c7fce14b1ad512a42abe33cb721a2ea3520d4b
> Author: Fan Li <fanl@mellanox.com>
> Date: Mon Dec 16 14:46:15 2019 +0200
>
> net/mlx5: Increase the max number of channels to 128
>
> I was expecting to be able to increase the number of channels on
> larger
> systems (e.g., 96 cpus), but that is not working as I expected.
>
this patch should help, unless you are limited by FW/system MSI-x ..
what is the amount of msix avaiable for eth0 port ?
businfo=$(ethtool -i eth0 | grep bus-info | cut -d":" -f2-)
cat /proc/interrupts | grep $businfo | wc -l
> This is on net-next as of today:
> 60bcbc41ffb3 ("Merge branch 'net-smc-add-and-delete-link-
> processing'")
>
> $ sudo ethtool -L eth0 combined 95
> Cannot set device channel parameters: Invalid argument
>
> As it stands the maximum is 63 (or is it 64 and cpus 0-63?):
> $ sudo ethtool -l eth0
> Channel parameters for eth0:
> Pre-set maximums:
> RX: 0
> TX: 0
> Other: 0
> Combined: 63
> Current hardware settings:
> RX: 0
> TX: 0
> Other: 0
> Combined: 63
>
So if number of msix is 64, we can only use 63 for data path
completions ..
do you have sriov enabled ?
what is the FW version you have ?
we need to figure out if this is a system MSIX limitation or a FW
limitation.
> A side effect of this limit is XDP_REDIRECT drops packets if a vhost
> thread gets scheduled on cpus 64 and up since the tx queue is based
> on
> processor id:
>
> int mlx5e_xdp_xmit(struct net_device *dev, int n, struct xdp_frame
> **frames,
> u32 flags)
> {
> ...
> sq_num = smp_processor_id();
> if (unlikely(sq_num >= priv->channels.num))
> return -ENXIO;
>
> So in my example if the redirect happens on cpus 64-95, which is 1/3
> of
> my hardware threads, the packet is just dropped.
>
Know XDP redirect issue, you need to tune the RSS and affinity on RX
side and match TX count and affinity on TX side, so you won't end up on
a wrong CPU on the TX side
> Am I missing something about how to use the expanded maximum?
>
> David
next prev parent reply other threads:[~2020-05-04 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 0:41 max channels for mlx5 David Ahern
2020-05-04 21:46 ` Saeed Mahameed [this message]
2020-05-04 23:04 ` David Ahern
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=2f5110e579a21737e5c13b23482eff6fdb6f3808.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
/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).