Re: [PATCH net-next 01/12] net: hns3: fix VLAN initialization to be compatible with port base insert VLAN

From: tanhuazhong
Date: Thu Apr 11 2019 - 22:31:01 EST




On 2019/4/12 2:20, David Miller wrote:
From: Huazhong Tan <tanhuazhong@xxxxxxxxxx>
Date: Thu, 11 Apr 2019 20:25:20 +0800

From: Jian Shen <shenjian15@xxxxxxxxxx>

This patch fixes VLAN initialization, in order to be compatible
with VLAN inserted base on port.

This doesn't mean anything to me.

Why was normal VLAN initialization different, and how is the behavior
of VLAN's configured when inserted based upon port different and why
is it better?

You have to improve your commit log messages so that someone not
intimately familiar with your driver and code can understand what you
are doing and why.


Sorry, I will describe it in detail.

Our hardware supports insert a specified vlan header for each function when send packets. User can enable it with command "ip link set <devname> vf <vfid> vlan <vlan id>". For this vlan header is inserted by hardware, not from stack, hardware also needs to strip it from received packet before upstreaming to stack. In this case, driver needs to tell hardware which vlan to insert or strip.

Thanks.

.