From: Simon Horman <simon.horman@corigine.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
david.m.ertman@intel.com, daniel.machon@microchip.com
Subject: Re: [PATCH net-next v2 00/10][pull request] ice: Implement support for SRIOV + LAG
Date: Fri, 28 Jul 2023 12:10:51 +0200 [thread overview]
Message-ID: <ZMOUK+jr0g1aGOr6@corigine.com> (raw)
In-Reply-To: <20230727195800.204461-1-anthony.l.nguyen@intel.com>
On Thu, Jul 27, 2023 at 12:57:50PM -0700, Tony Nguyen wrote:
> Dave Ertman says:
>
> 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.
>
> The ice-lag DDP must be loaded to support this feature.
>
> 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
> ---
> v2:
> - Move NULL check for q_ctx in ice_lag_qbuf_recfg() earlier (patch 6)
>
> v1: https://lore.kernel.org/netdev/20230726182141.3797928-1-anthony.l.nguyen@intel.com/
Thanks.
Reviewed-by: Simon Horman <simon.horman@corigine.com>
...
prev parent reply other threads:[~2023-07-28 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 19:57 [PATCH net-next v2 00/10][pull request] ice: Implement support for SRIOV + LAG Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 01/10] ice: Correctly initialize queue context values Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 02/10] ice: Add driver support for firmware changes for LAG Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 03/10] ice: changes to the interface with the HW and FW for SRIOV_VF+LAG Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 04/10] ice: implement lag netdev event handler Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 05/10] ice: process events created by " Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 06/10] ice: Flesh out implementation of support for SRIOV on bonded interface Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 07/10] ice: support non-standard teardown of bond interface Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 08/10] ice: enforce interface eligibility and add messaging for SRIOV LAG Tony Nguyen
2023-07-27 19:57 ` [PATCH net-next v2 09/10] ice: enforce no DCB config changing when in bond Tony Nguyen
2023-07-27 19:58 ` [PATCH net-next v2 10/10] ice: update reset path for SRIOV LAG support Tony Nguyen
2023-07-28 10:10 ` [PATCH net-next v2 00/10][pull request] ice: Implement support for SRIOV + LAG patchwork-bot+netdevbpf
2023-07-28 10:10 ` Simon Horman [this message]
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=ZMOUK+jr0g1aGOr6@corigine.com \
--to=simon.horman@corigine.com \
--cc=anthony.l.nguyen@intel.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).