From owner-freebsd-current@FreeBSD.ORG Mon Mar 15 16:14:21 2004 Return-Path: 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 10E1216A4CE; Mon, 15 Mar 2004 16:14:21 -0800 (PST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7556B43D2D; Mon, 15 Mar 2004 16:14:20 -0800 (PST) (envelope-from mikej@rogers.com) Received: from [192.168.0.1] ([63.139.3.63]) by fep03-mail.bloor.is.net.cable.rogers.comESMTP <20040316001417.CJZP411419.fep03-mail.bloor.is.net.cable.rogers.com@[192.168.0.1]>; Mon, 15 Mar 2004 19:14:17 -0500 Received: from 192.168.0.200 (SquirrelMail authenticated user mikej) by 192.168.0.1 with HTTP; Mon, 15 Mar 2004 19:14:16 -0500 (EST) Message-ID: <2659.192.168.0.200.1079396056.squirrel@192.168.0.1> In-Reply-To: <20040315234448.GA28383@Odin.AC.HMC.Edu> References: <2650.192.168.0.200.1079393908.squirrel@192.168.0.1> <20040315234448.GA28383@Odin.AC.HMC.Edu> Date: Mon, 15 Mar 2004 19:14:16 -0500 (EST) From: "Mike Jakubik" To: "Brooks Davis" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [63.139.3.63] using ID at Mon, 15 Mar 2004 19:14:17 -0500 cc: current@freebsd.org cc: net@freebsd.org Subject: Re: Byte counters reset at ~4GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 16 Mar 2004 00:14:21 -0000 Brooks Davis said: > > Please read the archives of freebsd-net. This has been discussed > many times. There are valid reasons for this, particularly the fact > that 64-bit counters are much more expensive to update on 32-bit > architectures. API breakage is also a problem. We're aware that 2^32 > is way to small a limit for modern network counters, but fixing it isn't > trivial on 32-bit hardware. Ok then, thats too bad. Sorry for the noise.