Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: "Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Cc: "Dziedziuch, SylwesterX" <sylwesterx.dziedziuch@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net v5 1/2] ice: Fix VSIs unable to share unicast MAC
Date: Wed, 20 Jul 2022 14:41:04 -0700	[thread overview]
Message-ID: <5b4ed9cb-c949-1d7a-2db6-8915f9171091@intel.com> (raw)
In-Reply-To: <DM6PR11MB27312AB61F71BAD0C920AC87F08E9@DM6PR11MB2731.namprd11.prod.outlook.com>



On 7/20/2022 6:15 AM, Jagielski, Jedrzej wrote:
>> On 7/18/2022 9:42 AM, Jedrzej Jagielski wrote:
>>> From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
>>>
>>> The driver currently does not allow two VSIs in the same PF domain
>>> to have the same unicast MAC address. This is incorrect in the sense
>>> that a policy decision is being made in the driver when it must be
>>> left to the user. This approach was causing issues when rebooting
>>> the system with VFs spawned not being able to change their MAC addresses.
>>> Such errors were present in dmesg:
>>>
>>> [ 7921.068237] ice 0000:b6:00.2 ens2f2: Unicast MAC 6a:0d:e4:70:ca:d1 already
>>> exists on this PF. Preventing setting VF 7 unicast MAC address to 6a:0d:e4:70:ca:d1
>>>
>>> Fix that by removing this restriction. Doing this also allows
>>> us to remove some additional code that's checking if a unicast MAC
>>> filter already exists.
>>>
>>> Rename ucast_shared to umac_shared, as "umac" is a more widely
>>> used shorthand for "unicast MAC".
>>
>> Since this will be removed, lets not thrash the driver with this rename.
>>
>>> Also add a helper function to set this flag. This helper is
>>> expected to be called by core drivers.
>>
>> and the helper.
> 
> OK, so can I resend the patch with no names changed and when the patch would
> be applied into the tree I would send the second one removing umac_shared?
> Is that a good approach?

Yes, that's exactly what I had in mind.

>>
>>> Fixes: 47ebc7b02485 ("ice: Check if unicast MAC exists before setting VF MAC")
>>> Signed-off-by: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
>>> Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
>>> Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
>>> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2022-07-20 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 16:42 [Intel-wired-lan] [PATCH net v5 1/2] ice: Fix VSIs unable to share unicast MAC Jedrzej Jagielski
2022-07-18 16:42 ` [Intel-wired-lan] [PATCH net v5 2/2] ice: Remove umac_shared Jedrzej Jagielski
2022-07-19 22:01   ` Tony Nguyen
2022-07-19 21:59 ` [Intel-wired-lan] [PATCH net v5 1/2] ice: Fix VSIs unable to share unicast MAC Tony Nguyen
2022-07-20 13:15   ` Jagielski, Jedrzej
2022-07-20 21:41     ` Tony Nguyen [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=5b4ed9cb-c949-1d7a-2db6-8915f9171091@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jedrzej.jagielski@intel.com \
    --cc=sylwesterx.dziedziuch@intel.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