netdev - Re: [PATCH mlx5-next 00/14] Mellanox, mlx5 next updates 2019-03-29

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1d87c70155d5fec885beaac9ac77e28f75076607.camel@mellanox.com>
Date:   Tue, 2 Apr 2019 19:51:14 +0000
From:   Saeed Mahameed <saeedm@...lanox.com>
To:     Leon Romanovsky <leonro@...lanox.com>,
        "saeed@...lanox.com" <saeed@...lanox.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
Subject: Re: [PATCH mlx5-next 00/14] Mellanox, mlx5 next updates 2019-03-29

On Fri, 2019-03-29 at 15:37 -0700, Saeed Mahameed wrote:
> Hi,
> 
> This series includes some misc shared code updates for mlx5-next
> branch.
> 
> From Maxim, Remove un-used macros and spinlock from mlx5 code.
> 
> From Aya, Expose Management PCIE info register layout and add rate
> limit
> print macros.
> 
> From Tariq, Compilation warning fix in fs_core.c
> 
> From Vu, Huy and Saeed, Improve mlx5 initialization flow:
> The goal is to provide a better logical separation of mlx5 core
> device initialization flow and will help to seamlessly support
> creating different mlx5 device types such as PF, VF and SF
> mlx5 sub-function virtual devices.
> 
> Mlx5_core driver needs to separate HCA resources from pci resources.
> Its initialize/load/unload will be broken into stages:
> 1. Initialize common data structures
> 2. Setup function which initializes pci resources (for PF/VF)
>    or some other specific resources for virtual device
> 3. Initialize software objects according to hardware capabilities
> 4. Load all mlx5_core components
> 
> It is also necessary to detach mlx5_core mdev name/message from pci
> device mdev->pdev name/message for a clearer report/debug of
> different mlx5 device types.
> 

Series applied to mlx5-next,

Thanks,
Saeed.