From owner-freebsd-net@FreeBSD.ORG Fri Nov 7 12:06:11 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADE1116A4CE for ; Fri, 7 Nov 2003 12:06:11 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id E094943FE3 for ; Fri, 7 Nov 2003 12:06:10 -0800 (PST) (envelope-from ahoff@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Fri, 7 Nov 2003 15:06:10 -0500 Message-ID: From: Alex Hoff To: "'freebsd-net@freebsd.org'" Date: Fri, 7 Nov 2003 15:06:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: 64 bit packet counters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 20:06:11 -0000 Hi, We are attempting to implement the IF-MIB, which requires the use of 64 bit packet counters and the differentiation between multicast and broadcast pkts. Since changing the if_data (by adding new counters and changing the existing to u_int64) is a bad idea, does anyone have any good ideas on how to do this? I was thinking of tacking on a new struct (lets call it ifx_data) on at the end of the current if_net struct with the appropriate counters (i/opacket, i/obyte, i/obcast, i/omcast). Apart from having to do a little double counting is there any obvious pitfals with this approach? Does anyone have an better ideas? Is there currently any plans to update the network stack to handle this properly? Thanks, Alex Hoff