From owner-freebsd-arch@FreeBSD.ORG  Thu Aug 29 06:46:54 2013
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 0F26FE7D;
 Thu, 29 Aug 2013 06:46:54 +0000 (UTC)
 (envelope-from bryanv@daemoninthecloset.org)
Received: from torment.daemoninthecloset.org (torment.daemoninthecloset.org
 [94.242.209.234])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C098F2912;
 Thu, 29 Aug 2013 06:46:53 +0000 (UTC)
Received: from sage.daemoninthecloset.org (unknown [70.114.209.60])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "sage.daemoninthecloset.org",
 Issuer "daemoninthecloset.org" (verified OK))
 by torment.daemoninthecloset.org (Postfix) with ESMTPS id DFBE342C08C6;
 Thu, 29 Aug 2013 08:52:03 +0200 (CEST)
X-Virus-Scanned: amavisd-new at daemoninthecloset.org
X-Virus-Scanned: amavisd-new at daemoninthecloset.org
Date: Thu, 29 Aug 2013 01:46:32 -0500 (CDT)
From: Bryan Venteicher <bryanv@daemoninthecloset.org>
To: Andre Oppermann <andre@freebsd.org>
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>
Subject: Re: Network stack changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.10.20]
X-Mailer: Zimbra 8.0.2_GA_5569 (ZimbraWebClient - GC20
 ([unknown])/8.0.2_GA_5569)
Thread-Topic: Network stack changes
Thread-Index: anDUShTn7iVw7wFEqZDuK6ld/6VXsQ==
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>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 06:46:54 -0000



----- 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())?