From owner-freebsd-amd64@freebsd.org  Wed Jun  1 13:43:46 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADF93B606FA
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed,  1 Jun 2016 13:43:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9E61E195D
 for <freebsd-amd64@FreeBSD.org>; Wed,  1 Jun 2016 13:43:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u51DhkGn002848
 for <freebsd-amd64@FreeBSD.org>; Wed, 1 Jun 2016 13:43:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209351] VLAN TX errors, possible performance regression after
 10.1-STABLE (r281235)
Date: Wed, 01 Jun 2016 13:43:46 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: gondim@bsdinfo.com.br
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209351-6-tNxUyri3Pg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209351-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209351-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 01 Jun 2016 14:38:18 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 13:43:46 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209351

gondim@bsdinfo.com.br changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gondim@bsdinfo.com.br

--- Comment #1 from gondim@bsdinfo.com.br ---
Hi,

I am the owner of the server. Thanks for your help in solving this problem.=
 I
believe that with the solution of this problem our FreeBSD will get stronge=
r,
providing more performance in demanding traffic.


Everything leads to believe that is related to a problem with vlan, but as =
I am
no developer can not say for sure if the problem is really that.

What I realized is that the connections without vlan, this problem does not
happen.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=