From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC 06/10] virtio: use software vlan stripping Date: Wed, 27 Aug 2014 11:04:52 -0700 Message-ID: <20140827110452.1cba26e3@urahara> References: <20140826020746.062748014@networkplumber.org> <20140826020848.386074683@networkplumber.org> <20140826092420.57e95493@urahara> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Ouyang, Changchun" Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Wed, 27 Aug 2014 05:42:09 +0000 "Ouyang, Changchun" wrote: > > > -----Original Message----- > > From: Stephen Hemminger [mailto:stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org] > > Sent: Wednesday, August 27, 2014 12:24 AM > > To: Ouyang, Changchun > > Cc: dev-VfR2kkLFssw@public.gmane.org > > Subject: Re: [RFC 06/10] virtio: use software vlan stripping > > > > On Tue, 26 Aug 2014 08:37:11 +0000 > > "Ouyang, Changchun" wrote: > > > > > Hi Stephen, > > > > > > Would you please describe the use scenario for the front end rx vlan strip > > and tx vlan insertion? > > > In our current implementation, backend will strip vlan tag for RX, and insert > > vlan tag for TX. > > > > > > Thanks > > > Changchun > > > > First, we don't have to do software VLAN strip on our backend if we do this. > > And this way we can always use VLAN insert on transmit. Otherwise you > > have to introduce special case because there is no DPDK API to determine if > > device does or does not do VLAN handling. > > > > How the virtio frontend tell backend whether it has software VLAN strip feature or not? > It seems no feature bit to negotiate it. > > Thanks > Changchun > All other drivers have VLAN stripping as option under rte_eth_rxmode / hw_vlan_strip. There is negotiation in DPDK, it is strictly ask for feature and either get it or an error. Therefore we went ahead and emulated the feature in software.