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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 Jun 2014 13:01:29 +0530 From: Sathya Perla <sathya.perla@...lex.com> To: <netdev@...r.kernel.org> Subject: [PATCH net-next v2 0/4] be2net: patch set v2 change: merged 2 lines into one in patch 4 Patch 1 refactors be_cmd_get_profile_config() routine to reduce code duplication by using the be_cmd_notify_wait() routine, instead of using a separate variant of the code for MBOX and MCCQ. Patch 2 introduces the required FW-cmd code in the PF to query RSS support on a VF. This is in preparation for patch 3. Patch 3 adds support for the PF driver to re-configure the resource distribution in FW based on the number of VFs enabled by the user. When the user is not interested in enabling VFs, all resources of a port are set-aside for the PF. If less than maximum number of VFs are enabled, then each VF gets a better share of the resources and can now enable RSS (if the interface supports it.) Patch 4 is a minor fix to re-enable HW vlan filtering as soon as the number of vlans programmed is within the HW limit. Please consider applying to net-next tree. Thanks! Kalesh AP (1): be2net: re-enable vlan filtering mode asap Vasundhara Volam (3): be2net: remove be_cmd_get_profile_config_mbox/mccq() variants be2net: read VF's capabilities from GET_PROFILE_CONFIG cmd be2net: create optimal number of queues on SR-IOV config drivers/net/ethernet/emulex/benet/be.h | 9 +- drivers/net/ethernet/emulex/benet/be_cmds.c | 226 ++++++++++++++++----------- drivers/net/ethernet/emulex/benet/be_cmds.h | 9 +- drivers/net/ethernet/emulex/benet/be_main.c | 141 ++++++++++------- 4 files changed, 230 insertions(+), 155 deletions(-) -- 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
Powered by blists - more mailing lists