netdev - Re: [PATCH net-next 2/4] net/mlx5_core: Use hardware registers description header file

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Sep 2014 08:34:49 -0700
From:	Alexei Starovoitov <alexei.starovoitov@...il.com>
To:	Eli Cohen <eli@....mellanox.co.il>
Cc:	davem@...emloft.net, netdev@...r.kernel.org, ogerlitz@...lanox.com,
	yevgenyp@...lanox.com, Eli Cohen <eli@...lanox.com>
Subject: Re: [PATCH net-next 2/4] net/mlx5_core: Use hardware registers
 description header file

On Tue, Sep 30, 2014 at 04:02:13PM +0300, Eli Cohen wrote:
> Add an auto generated header file that describes hardware registers along with
> set of macros that set/get values. The macros do static checks to avoid
> overflow, handle endianess, and overall provide a clean way to code commands.
> 
> A few commands were removed since they are not supported currently and will be
> added when support is available.
> 
> Signed-off-by: Eli Cohen <eli@...lanox.com>
> ---
>  drivers/net/ethernet/mellanox/mlx5/core/cmd.c |   36 -
>  drivers/net/ethernet/mellanox/mlx5/core/qp.c  |    3 -
>  include/linux/mlx5/device.h                   |   74 +
>  include/linux/mlx5/driver.h                   |   76 +-
>  include/linux/mlx5/mlx5_ifc.h                 | 4464 +++++++++++++++++++++++++
>  5 files changed, 4539 insertions(+), 114 deletions(-)

I find hard time believing that all of 4k auto generated macros
are actually used. Could you trim it down to only usable bits?

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html