From owner-freebsd-current@FreeBSD.ORG Sun Jan 8 11:33:47 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8F1A16A41F for ; Sun, 8 Jan 2006 11:33:47 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F12B743D4C for ; Sun, 8 Jan 2006 11:33:46 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 59206 invoked from network); 8 Jan 2006 11:37:02 -0000 Received: from c00l3r.networx.ch (HELO freebsd.org) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 8 Jan 2006 11:37:02 -0000 Message-ID: <43C0F89B.7FC19C0F@freebsd.org> Date: Sun, 08 Jan 2006 12:33:47 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Massimo Lusetti References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> <43BFEB2E.4040303@freebsd.org> <200601071940.k07JeHt3095158@apollo.backplane.com> <43C02362.2070009@samsco.org> <1136717948.4312.5.camel@massimo.datacode.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Patch for 1mpps on if_em (was: FreeBSD handles leapsecondcorrectly) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2006 11:33:47 -0000 Massimo Lusetti wrote: > > On Sat, 2006-01-07 at 13:24 -0700, Scott Long wrote: > > > I'm about to release a patch to Andre that should allow if_em to fast > > forward 1mpps or more on his hardware, using no shortcuts or hacks other > > than the inherent shortcut that the ffwd code provides. The approach > > I'm taking also works on the other high performance network interfaces. > > There is also a lot of work going on to streamline the ifnet layer that > > will likely result in several hundred nanoseconds of latency being > > removed from there. I'd personally love to see DragonFly approach this > > Will all this great stuff end up in RELENG_6 branch? Some of it but not all. Those things which are driver optimizations and other detail stuff will be backported. Stuff that does architectual and API/ABI changes will not. We are not allowed to break the API/ABI within a -STABLE series. > That's very good news (TM) to hear... Indeed. I have tons of measurements and data from the test runs which has to be processed. Once that is done we can start to reach firm conclusions and to tackle all the other items which put some breaks on the performance. -- Andre