Commit 8bc8d188 authored by Brett Creeley's avatar Brett Creeley Committed by Jeff Kirsher

ice: Update comment for ice_fltr_mgmt_list_entry

Previously the comment stated that VSI lists should be used when a
second VSI becomes a subscriber to the "VLAN address". VSI lists
are always used for VLAN membership, so replace "VLAN address" with
"MAC address". Also note that VLAN(s) always use VSI list rules.
Signed-off-by: default avatarBrett Creeley <brett.creeley@intel.com>
Signed-off-by: default avatarAnirudh Venkataramanan <anirudh.venkataramanan@intel.com>
Tested-by: default avatarAndrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: default avatarJeff Kirsher <jeffrey.t.kirsher@intel.com>
parent b2ccf317
...@@ -140,7 +140,8 @@ struct ice_fltr_list_entry { ...@@ -140,7 +140,8 @@ struct ice_fltr_list_entry {
/* This defines an entry in the list that maintains MAC or VLAN membership /* This defines an entry in the list that maintains MAC or VLAN membership
* to HW list mapping, since multiple VSIs can subscribe to the same MAC or * to HW list mapping, since multiple VSIs can subscribe to the same MAC or
* VLAN. As an optimization the VSI list should be created only when a * VLAN. As an optimization the VSI list should be created only when a
* second VSI becomes a subscriber to the VLAN address. * second VSI becomes a subscriber to the same MAC address. VSI lists are always
* used for VLAN membership.
*/ */
struct ice_fltr_mgmt_list_entry { struct ice_fltr_mgmt_list_entry {
/* back pointer to VSI list id to VSI list mapping */ /* back pointer to VSI list id to VSI list mapping */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment