Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: disable stripping in default VSI ctx
Date: Fri, 27 May 2022 18:17:15 +0200	[thread overview]
Message-ID: <4f8d2b55-ed19-206e-3171-efff363dc8d4@linux.intel.com> (raw)
In-Reply-To: <c808f098-2d17-db32-6106-8c75d5116508@molgen.mpg.de>



On 27-May-22 15:11, Paul Menzel wrote:
> Dear Marcin.
> 
> 
> Am 27.05.22 um 15:01 schrieb Marcin Szycik:
> 
>> On 27-May-22 14:15, Paul Menzel wrote:
> 
>>> Am 27.05.22 um 13:51 schrieb Marcin Szycik:
>>>> From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>>>>
>>>> In case when driver is in eswitch mode, having VLAN stripping enabled
>>>> causes failure in communication. All VLAN configuration commands are
>>>> blocked, because of that VF driver can't disable VLAN stripping at
>>>
>>> s/blocked, because/blocked. Because/
>>
>> Sorry, but I don't understand what to change here. Could you explain more clearly?
> 
> I am sorry for being unclear. I think it should be two sentences.

Ah, now I see it's a sed-style string replace. I will remember this for future discussions :)

>>>> initialization. It leads to the situation when VLAN stripping on VF VSI
>>>> is on, but in kernel it is off.
>>>>
>>>> To prevent this, set VLAN stripping to disabled in VSI initialization.
>>>
>>> Maybe: ?, disable VLAN stripping in VSI initialization.
>>
>> Sounds good.
>>
>>>> It doesn't break other usecases, because it is set according to kernel
>>>> settings.
>>>
>>> Please document your test setup.
>>
>> Will reproduction steps be enough?
> 
> Yes, that?d be great.

I'll send v2 probably on Monday. I'm sorry for delay, but I have a bit of a problem reproducing this issue, and I don't want to include a repro that doesn't actually work (Micha? originally worked on the fix, but he will be unavailable for some time).

Regards,
Marcin

>>>> Fixes: f09901aa554a ("ice: remove VLAN representor specific ops")
>>>> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>>>> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
>>>> ---
>>>> ?? drivers/net/ethernet/intel/ice/ice_lib.c | 3 +++
>>>> ?? 1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/drivers/net/ethernet/intel/ice/ice_lib.c b/drivers/net/ethernet/intel/ice/ice_lib.c
>>>> index 70961c0343e7..b28fb8eacffb 100644
>>>> --- a/drivers/net/ethernet/intel/ice/ice_lib.c
>>>> +++ b/drivers/net/ethernet/intel/ice/ice_lib.c
>>>> @@ -887,6 +887,9 @@ static void ice_set_dflt_vsi_ctx(struct ice_hw *hw, struct ice_vsi_ctx *ctxt)
>>>> ?????????????? (ICE_AQ_VSI_OUTER_TAG_VLAN_8100 <<
>>>> ??????????????? ICE_AQ_VSI_OUTER_TAG_TYPE_S) &
>>>> ?????????????? ICE_AQ_VSI_OUTER_TAG_TYPE_M;
>>>> +??????? ctxt->info.outer_vlan_flags |=
>>>> +??????????? FIELD_PREP(ICE_AQ_VSI_OUTER_VLAN_EMODE_M,
>>>> +?????????????????? ICE_AQ_VSI_OUTER_VLAN_EMODE_NOTHING);
>>>> ?????? }
>>>> ?????? /* Have 1:1 UP mapping for both ingress/egress tables */
>>>> ?????? table |= ICE_UP_TABLE_TRANSLATE(0, 0)
>> _______________________________________________
>> Intel-wired-lan mailing list
>> Intel-wired-lan at osuosl.org
>> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-05-27 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 11:51 [Intel-wired-lan] [PATCH net] ice: disable stripping in default VSI ctx Marcin Szycik
2022-05-27 12:15 ` Paul Menzel
2022-05-27 13:01   ` Marcin Szycik
2022-05-27 13:11     ` Paul Menzel
2022-05-27 16:17       ` Marcin Szycik [this message]
2022-05-27 16:31 ` Tony Nguyen
2022-05-30 11:25   ` Marcin Szycik

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=4f8d2b55-ed19-206e-3171-efff363dc8d4@linux.intel.com \
    --to=marcin.szycik@linux.intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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