From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, Yuying" <yuying.zhang@intel.com>,
"Liu, KevinX" <kevinx.liu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"Yang, SteveX" <stevex.yang@intel.com>,
"Zhang, RobinX" <robinx.zhang@intel.com>
Subject: RE: [PATCH v7] net/i40e: add outer VLAN processing
Date: Wed, 15 Jun 2022 12:12:33 +0000 [thread overview]
Message-ID: <DM4PR11MB59943EAB8DA2EBDEAF55ED26D7AD9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM6PR11MB3516AAFF9DE46888725E17E98EAA9@DM6PR11MB3516.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Zhang, Yuying <yuying.zhang@intel.com>
> Sent: Tuesday, June 14, 2022 4:40 PM
> To: Liu, KevinX <kevinx.liu@intel.com>; dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Yang, SteveX
> <stevex.yang@intel.com>; Zhang, RobinX <robinx.zhang@intel.com>
> Subject: RE: [PATCH v7] net/i40e: add outer VLAN processing
>
> Hi Kevin,
>
> Workaround should be replaced when root cause be found.
>
> Best regards,
> Yuying
>
> > -----Original Message-----
> > From: Liu, KevinX <kevinx.liu@intel.com>
> > Sent: Tuesday, June 14, 2022 11:07 AM
> > To: Zhang, Yuying <yuying.zhang@intel.com>; dev@dpdk.org
> > Cc: Xing, Beilei <beilei.xing@intel.com>; Yang, SteveX
> > <stevex.yang@intel.com>; Zhang, RobinX <robinx.zhang@intel.com>
> > Subject: RE: [PATCH v7] net/i40e: add outer VLAN processing
> >
> > Hi, Yuying
> >
> > > -----Original Message-----
> > > From: Zhang, Yuying <yuying.zhang@intel.com>
> > > Sent: 2022年6月14日 10:44
> > > To: Liu, KevinX <kevinx.liu@intel.com>; dev@dpdk.org
> > > Cc: Xing, Beilei <beilei.xing@intel.com>; Yang, SteveX
> > > <stevex.yang@intel.com>; Zhang, RobinX <robinx.zhang@intel.com>
> > > Subject: RE: [PATCH v7] net/i40e: add outer VLAN processing
> > >
> > > Hi Kevin,
> > >
> > > > -----Original Message-----
> > > > From: Liu, KevinX <kevinx.liu@intel.com>
> > > > Sent: Saturday, June 11, 2022 12:30 AM
> > > > To: dev@dpdk.org
> > > > Cc: Zhang, Yuying <yuying.zhang@intel.com>; Xing, Beilei
> > > > <beilei.xing@intel.com>; Yang, SteveX <stevex.yang@intel.com>;
> > > > Zhang, RobinX <robinx.zhang@intel.com>; Liu, KevinX
> > > > <kevinx.liu@intel.com>
> > > > Subject: [PATCH v7] net/i40e: add outer VLAN processing
> > > >
> > > > From: Robin Zhang <robinx.zhang@intel.com>
> > > >
> > > > Outer VLAN processing is supported after firmware v8.4, kernel
> > > > driver also
> > >
> > > Since this patch can only be enabled with firmware v8.6, should you
> > > sync with dpdk here?
> > OK, I'll revise it here.
> > >
> > > > change the default behavior to support this feature. To align with
> > > > kernel driver, add support for outer VLAN processing in DPDK.
> > > >
> > > > But it is forbidden for firmware to change the Inner/Outer VLAN
> > > > configuration while there are MAC/VLAN filters in the switch table.
> > > > Therefore, we need to clear the MAC table before setting config,
> > > > and then restore the MAC table after setting.
> > > >
> > > > This will not impact on an old firmware.
> > > >
> > > > Signed-off-by: Robin Zhang <robinx.zhang@intel.com>
> > > > Signed-off-by: Kevin Liu <kevinx.liu@intel.com>
>
> Acked-by: Yuying Zhang <yuying.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2022-06-15 12:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 9:39 [PATCH] " Robin Zhang
2022-05-19 6:18 ` [PATCH v2] " Robin Zhang
2022-06-09 11:26 ` [PATCH v3] " Kevin Liu
2022-06-09 14:43 ` [PATCH v4] " Kevin Liu
2022-04-07 20:01 ` [PATCH v5] " Kevin Liu
2022-06-10 15:52 ` [PATCH v6] " Kevin Liu
2022-06-10 8:06 ` Zhang, Qi Z
2022-06-10 8:14 ` Liu, KevinX
2022-06-10 16:29 ` [PATCH v7] " Kevin Liu
2022-06-10 14:27 ` Ben Magistro
2022-06-13 2:14 ` Liu, KevinX
2022-06-13 15:01 ` Ben Magistro
2022-06-14 2:43 ` Zhang, Yuying
2022-06-14 3:06 ` Liu, KevinX
2022-06-14 8:39 ` Zhang, Yuying
2022-06-14 8:43 ` Liu, KevinX
2022-06-15 12:12 ` Zhang, Qi Z [this message]
2022-06-10 1:01 ` [PATCH v4] " Zhang, Qi Z
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=DM4PR11MB59943EAB8DA2EBDEAF55ED26D7AD9@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=kevinx.liu@intel.com \
--cc=robinx.zhang@intel.com \
--cc=stevex.yang@intel.com \
--cc=yuying.zhang@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;
as well as URLs for NNTP newsgroup(s).