From owner-cvs-src@FreeBSD.ORG Wed Jan 26 12:55:59 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5464316A4CE; Wed, 26 Jan 2005 12:55:59 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8814243D1F; Wed, 26 Jan 2005 12:55:58 +0000 (GMT) (envelope-from maxim@FreeBSD.org) Received-SPF: pass (mp2.macomnet.net: domain of maxim@FreeBSD.org designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@FreeBSD.org; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id j0QCtuRs048407; Wed, 26 Jan 2005 15:55:57 +0300 (MSK) (envelope-from maxim@FreeBSD.org) Date: Wed, 26 Jan 2005 15:55:56 +0300 (MSK) From: Maxim Konovalov To: Robert Watson In-Reply-To: Message-ID: <20050126155227.P47994@mp2.macomnet.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (201/050124) X-SpamTest-Info: Profile: Detect Hard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking - Keywords (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0124], SpamtestISP/Release cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/em if_em.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 12:55:59 -0000 On Wed, 26 Jan 2005, 12:12-0000, Robert Watson wrote: > On Wed, 26 Jan 2005, Maxim Konovalov wrote: > > > > Disable use of hardware VLAN tagging and stripping in if_em in > > > the default configuration: it appears to work properly in the > > > non-promiscuous case, but we've not yet implemented a more > > > general solution that maintains full functionality with > > > promiscuous mode enabled. While my hope is that we can get > > > one implemented soon, this will improve functionality > > > substantially in the mean time. > > > > Thanks! > > Sorry this has taken so long -- I hoped to put together a solution > in December, but ran out of time. We may want to make the same > change to if_re, which probably suffers from the same problem (I'm > unable to test that, since I have no if_re hardware). Hopefully I Thanks for the hint! A friend of mine complaned about re(4) instability recently. -- Maxim Konovalov