netdev - [net-next patch 0/2] bnx2x: Enable cnic at run-time

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

Date:	Wed, 7 Nov 2012 12:45:46 +0200
From:	"Merav Sicron" <meravs@...adcom.com>
To:	davem@...emloft.net
cc:	netdev@...r.kernel.org, eilong@...adcom.com,
	"Merav Sicron" <meravs@...adcom.com>
Subject: [net-next patch 0/2] bnx2x: Enable cnic at run-time

Hi Dave,

This patch series removes the BCM_CNIC bnx2x define, and eliminates the use of
the CONFIG_CNIC kconfig option.
The define removal is mainly important for SR-IOV, as the VF driver will use the
same code as the PF/hypervisor driver. Since storage is not supported in
SR-IOV (while is usually enabled in the non SR-IOV driver), we don't want to
waste resources on it.
After this change, cnic-related resources are allocated only when the cnic
module registers with bnx2x (which means that the user asked for storage
services). Also only at this stage the HW is configured to non-NIC (offload)
mode.
The first patch is the driver-FW HSI addition to change the 'update' ramrod for
offload mode configuration at run-time.
The second patch is for the removal of the BCM_CNIC define, and for separating
the load flow to two stages, one for L2 and one for cnic-related stuff.

Please consider applying this patch series to net-next.

Thanks,
Merav

--
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