netdev - Re: [PATCH rdma-next v1 0/5] Introduce dynamic UAR allocation mode

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]

Date:   Fri, 27 Mar 2020 13:08:06 -0300
From:   Jason Gunthorpe <jgg@...pe.ca>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Doug Ledford <dledford@...hat.com>,
        Leon Romanovsky <leonro@...lanox.com>,
        linux-rdma@...r.kernel.org,
        Michael Guralnik <michaelgur@...lanox.com>,
        netdev@...r.kernel.org, Saeed Mahameed <saeedm@...lanox.com>,
        Yishai Hadas <yishaih@...lanox.com>
Subject: Re: [PATCH rdma-next v1 0/5] Introduce dynamic UAR allocation mode

On Tue, Mar 24, 2020 at 08:01:38AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...lanox.com>
> 
> Changelog:
> v1: * Added patch that moved mlx5_bfreg_info from global header to the mlx5_ib.h
>     * No other changes.
> v0: * https://lore.kernel.org/linux-rdma/20200318124329.52111-1-leon@kernel.org
> 
> ----------------------------------------------------------------------------------
> 
> >From Yishai,
> 
> This series exposes API to enable a dynamic allocation and management of a
> UAR which now becomes to be a regular uobject.
> 
> Moving to that mode enables allocating a UAR only upon demand and drop the
> redundant static allocation of UARs upon context creation.
> 
> In addition, it allows master and secondary processes that own the same command
> FD to allocate and manage UARs according to their needs, this can’t be achieved
> today.
> 
> As part of this option, QP & CQ creation flows were adapted to support this
> dynamic UAR mode once asked by user space.
> 
> Once this mode is asked by mlx5 user space driver on a given context, it will
> be mutual exclusive, means both the static and legacy dynamic modes for using
> UARs will be blocked.
> 
> The legacy modes are supported for backward compatible reasons, looking
> forward we expect this new mode to be the default.
> 
> Thanks
> 
> Leon Romanovsky (1):
>   IB/mlx5: Limit the scope of struct mlx5_bfreg_info to mlx5_ib
> 
> Yishai Hadas (4):
>   IB/mlx5: Expose UAR object and its alloc/destroy commands
>   IB/mlx5: Extend CQ creation to get uar page index from user space
>   IB/mlx5: Extend QP creation to get uar page index from user space
>   IB/mlx5: Move to fully dynamic UAR mode once user space supports it

Applied to for-next, thanks

Jason