netdev - Re: [PATCH net-next] net/mlx4_core: Respond to operation request by firmware

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: <20130729.011253.1064287168678653852.davem@davemloft.net>
Date:	Mon, 29 Jul 2013 01:12:53 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	amirv@...lanox.com
Cc:	netdev@...r.kernel.org, ogerlitz@...lanox.com,
	yevgenyp@...lanox.com, jackm@....mellanox.com, eugenia@...lanox.com
Subject: Re: [PATCH net-next] net/mlx4_core: Respond to operation request
 by firmware

From: Amir Vadai <amirv@...lanox.com>
Date: Sun, 28 Jul 2013 18:54:21 +0300

> From: Yevgeny Petrilin <yevgenyp@...lanox.com>
> 
> This commit adds new firmware command and new firmware event.  The firmware
> raises the MLX4_EVENT_TYPE_OP_REQUIRED event in order to signal the driver it
> needs to perform an administrative operation throughout the MLX4_CMD_GET_OP_REQ
> command. At the moment the supported operation is adding/removing multicast
> entries which are used by the firmware for handling NCSI traffic in B0
> steering mode.
> 
> Also, had to swap the order of mlx4_init_mcg_table() and
> mlx4_init_eq_table() to make sure that driver will get events only after
> resources are initialized to handle it.
> 
> Signed-off-by: Yevgeny Petrilin <yevgenyp@...lanox.com>
> Signed-off-by: Jack Morgenstein <jackm@....mellanox.com>
> Signed-off-by: Eugenia Emantayev <eugenia@...lanox.com>
> Signed-off-by: Amir Vadai <amirv@...lanox.com>

Applied, thanks.
--
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