netdev - Re: [net-next 10/14] net/mlx5: Let user configure io_eq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a8dfcb9f-8d06-a240-c532-dad0ed724ecb@linux.dev>
Date:   Wed, 27 Oct 2021 09:16:41 +0300
From:   Gal Pressman <gal.pressman@...ux.dev>
To:     Jakub Kicinski <kuba@...nel.org>,
        Saeed Mahameed <saeedm@...dia.com>
Cc:     Jiri Pirko <jiri@...dia.com>, Moshe Shemesh <moshe@...dia.com>,
        Shay Drory <shayd@...dia.com>, Parav Pandit <parav@...dia.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [net-next 10/14] net/mlx5: Let user configure io_eq_size param

On 26/10/2021 20:16, Jakub Kicinski wrote:
> On Tue, 26 Oct 2021 15:54:28 +0000 Saeed Mahameed wrote:
>> On Tue, 2021-10-26 at 08:05 -0700, Jakub Kicinski wrote:
>>> On Mon, 25 Oct 2021 13:54:27 -0700 Saeed Mahameed wrote:  
>>>> From: Shay Drory <shayd@...dia.com>
>>>>
>>>> Currently, each I/O EQ is taking 128KB of memory. This size
>>>> is not needed in all use cases, and is critical with large scale.
>>>> Hence, allow user to configure the size of I/O EQs.
>>>>
>>>> For example, to reduce I/O EQ size to 64, execute:
>>>> $ devlink resource set pci/0000:00:0b.0 path /io_eq_size/ size 64
>>>> $ devlink dev reload pci/0000:00:0b.0  
>>> This sort of config is needed by more drivers,
>>> we need a standard way of configuring this.
>> We had a debate internally about the same thing, Jiri and I thought
>> that EQ might be a ConnectX only thing (maybe some other vendors have
>> it) but it is not really popular
> I thought it's a RDMA thing. At least according to grep there's 
> a handful of non-MLX drivers which have eqs. Are these not actual
> event queues? (huawei/hinic, ibm/ehea, microsoft/mana, qlogic/qed)


These are indeed event queues in RDMA, but it's more of an
implementation detail in each driver, there's no EQ object definition in
the IB spec AFAIK.