From: Dave Ertman <david.m.ertman@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, bcreeley@amd.com,
daniel.machon@microchip.com, simon.horman@corigine.com
Subject: [Intel-wired-lan] [PATCH iwl-next v5 00/10] Implement support for SRIOV + LAG
Date: Thu, 15 Jun 2023 09:29:22 -0700 [thread overview]
Message-ID: <20230615162932.762756-1-david.m.ertman@intel.com> (raw)
Implement support for SRIOV VF's on interfaces that are in an
aggregate interface.
The first interface added into the aggregate will be flagged as
the primary interface, and this primary interface will be
responsible for managing the VF's resources. VF's created on the
primary are the only VFs that will be supported on the aggregate.
Only Active-Backup mode will be supported and only aggregates whose
primary interface is in switchdev mode will be supported.
Additional restrictions on what interfaces can be added to the aggregate
and still support SRIOV VFs are:
- interfaces have to all be on the same physical NIC
- all interfaces have to have the same QoS settings
- interfaces have to have the FW LLDP agent disabled
- only the primary interface is to be put into switchdev mode
- no more than two interfaces in the aggregate
Changes since v1:
Fix typo in commit message
Fix typos in warning messages
Fix typo in function header
Use correct bitwise operator instead of boolean
Changes since v2:
Rebase on current next-queue
Fix typos in commits
Fix typos in function headers
use %u for unsigned values in debug message
Refactor common code in node moves to subfunction
Changes since v3:
Fix typos in warning messages
move refactor of common code to earlier patch
expand use of refactored code
move prototype and func call into patch that defines func
Changes since v4:
Change module_init to use goto unwind approach
Change function name to be more descriptive
chagen variable to be more scope specific
Make sure non-feature specific functions are still performed
Free correct memory
Fix typos in warning messages
added check for invalid TEID in queue cfg
Dave Ertman (9):
ice: Add driver support for firmware changes for LAG
ice: changes to the interface with the HW and FW for SRIOV_VF+LAG
ice: implement lag netdev event handler
ice: process events created by lag netdev event handler
ice: Flesh out implementation of support for SRIOV on bonded interface
ice: support non-standard teardown of bond interface
ice: enforce interface eligibility and add messaging for SRIOV LAG
ice: enforce no DCB config changing when in bond
ice: update reset path for SRIOV LAG support
Jacob Keller (1):
ice: Correctly initialize queue context values
drivers/net/ethernet/intel/ice/ice.h | 5 +
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 53 +-
drivers/net/ethernet/intel/ice/ice_common.c | 56 +
drivers/net/ethernet/intel/ice/ice_common.h | 4 +
drivers/net/ethernet/intel/ice/ice_dcb_nl.c | 50 +
drivers/net/ethernet/intel/ice/ice_lag.c | 1840 ++++++++++++++++-
drivers/net/ethernet/intel/ice/ice_lag.h | 34 +-
drivers/net/ethernet/intel/ice/ice_lib.c | 2 +-
drivers/net/ethernet/intel/ice/ice_lib.h | 1 +
drivers/net/ethernet/intel/ice/ice_main.c | 36 +-
drivers/net/ethernet/intel/ice/ice_sched.c | 37 +-
drivers/net/ethernet/intel/ice/ice_sched.h | 21 +
drivers/net/ethernet/intel/ice/ice_switch.c | 88 +-
drivers/net/ethernet/intel/ice/ice_switch.h | 29 +
drivers/net/ethernet/intel/ice/ice_type.h | 2 +
drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +
16 files changed, 2125 insertions(+), 135 deletions(-)
--
2.40.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-06-15 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 16:29 Dave Ertman [this message]
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 01/10] ice: Correctly initialize queue context values Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 02/10] ice: Add driver support for firmware changes for LAG Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 03/10] ice: changes to the interface with the HW and FW for SRIOV_VF+LAG Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 04/10] ice: implement lag netdev event handler Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 05/10] ice: process events created by " Dave Ertman
2023-06-16 20:47 ` Tony Nguyen
2023-06-20 16:07 ` Ertman, David M
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 06/10] ice: Flesh out implementation of support for SRIOV on bonded interface Dave Ertman
2023-06-16 20:56 ` Tony Nguyen
2023-06-20 16:07 ` Ertman, David M
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 07/10] ice: support non-standard teardown of bond interface Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 08/10] ice: enforce interface eligibility and add messaging for SRIOV LAG Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 09/10] ice: enforce no DCB config changing when in bond Dave Ertman
2023-06-15 16:29 ` [Intel-wired-lan] [PATCH iwl-next v5 10/10] ice: update reset path for SRIOV LAG support Dave Ertman
-- strict thread matches above, loose matches on Subject: below --
2023-06-20 18:34 [Intel-wired-lan] [PATCH iwl-next v5 00/10] Implement support for SRIOV + LAG Dave Ertman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230615162932.762756-1-david.m.ertman@intel.com \
--to=david.m.ertman@intel.com \
--cc=bcreeley@amd.com \
--cc=daniel.machon@microchip.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox