Many thanks for the sharing. Yes, as you pointed out, it might not worthwhile
to do offload for vlan.
Regards,
Kingwel
From: Damjan Marion
Sent: Monday, January 07, 2019 9:18 PM
To: Kingwel Xie
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] ethernet-input on master branch
On 7 Jan 2019
> On 7 Jan 2019, at 12:38, Kingwel Xie wrote:
>
> thanks, Damjan, that is very clear. I checked the device-input and
> ethernet-input code, and yes I totally understand your point.
>
> Two more questions, I can see you spend some time on avf plugin, do you think
> it will eventually become
?
For vlan tagging, would you like to consider using the HW rx and tx offload to
optimize the vlan sub-interface?
Reagrds,
Kingwel
原始邮件
主题： Re: [vpp-dev] ethernet-input on master branch
来自： "Damjan Marion via Lists.Fd.Io"
发至： 2019年1月7日 下午5:23
抄送： Kingwel Xie
On 5 Jan 2019
> On 5 Jan 2019, at 04:55, Kingwel Xie wrote:
>
> Hi Damjan,
>
> I noticed you removed the quick path from dpdk-input to ip-input/mpls-input,
> after you merged the patch of ethernet-input optimization. Therefore, all
> packets now have to go through ethernet-input. It would take a few
Hi Damjan,
I noticed you removed the quick path from dpdk-input to ip-input/mpls-input,
after you merged the patch of ethernet-input optimization. Therefore, all
packets now have to go through ethernet-input. It would take a few more cpu
clocks than before.
Please elaborate why making this
