Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Aug 2013 01:46:32 -0500 (CDT)
From:      Bryan Venteicher <bryanv@daemoninthecloset.org>
To:        Andre Oppermann <andre@freebsd.org>
Cc:        "Alexander V. Chernikov" <melifaro@yandex-team.ru>, adrian@freebsd.org, freebsd-hackers@freebsd.org, freebsd-arch@freebsd.org, luigi@freebsd.org, ae@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org>, FreeBSD Net <net@freebsd.org>
Subject:   Re: Network stack changes
Message-ID:  <2112475076.435.1377758792082.JavaMail.root@daemoninthecloset.org>
In-Reply-To: <521E78B0.6080709@freebsd.org>
References:  <521E41CB.30700@yandex-team.ru> <521E78B0.6080709@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help


----- Original Message -----
> On 28.08.2013 20:30, Alexander V. Chernikov wrote:
> > Hello list!
> 
> Hello Alexander,
> 
> you sent quite a few things in the same email.  I'll try to respond
> as much as I can right now.  Later you should split it up to have
> more in-depth discussions on the individual parts.
> 
<trim>
> 
> > We already have some capabilities like VLANHWFILTER/VLANHWTAG, we can add
> > some more. We even have
> > per-driver hooks to program HW filtering.
> 
> We could.  Though for vlan it looks like it would be easier to remove the
> hardware vlan tag stripping and insertion.  It only adds complexity in all
> drivers for no gain.
> 

In the shorter term, can we remove the requirement for the parent
interface to support IFCAP_VLAN_HWTAGGING in order to do checksum
offloading on the VLAN interface (see vlan_capabilities())?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2112475076.435.1377758792082.JavaMail.root>