From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267370AbUBRUoL (ORCPT ); Wed, 18 Feb 2004 15:44:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267378AbUBRUoL (ORCPT ); Wed, 18 Feb 2004 15:44:11 -0500 Received: from kiuru.kpnet.fi ([193.184.122.21]:61322 "EHLO kiuru.kpnet.fi") by vger.kernel.org with ESMTP id S267370AbUBRUoG (ORCPT ); Wed, 18 Feb 2004 15:44:06 -0500 Subject: Re: [NET] 64 bit byte counter for 2.6.3 From: Markus =?ISO-8859-1?Q?H=E4stbacka?= To: root@chaos.analogic.com Cc: Kernel Mailinglist , netdev@oss.sgi.com In-Reply-To: References: <1077123078.9223.7.camel@midux> <20040218101711.25dda791@dell_ss3.pdx.osdl.net> Content-Type: text/plain Message-Id: <1077137014.18843.10.camel@midux> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 18 Feb 2004 22:43:34 +0200 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2004-02-18 at 22:32, Richard B. Johnson wrote: > Manipulation of a 'long long' is not atomic in 32 bit architectures. > Please explain how we don't care, if we shouldn't care. Also some > /proc entries might get read incorrectly with existing tools. Please, tell me all the tools, I'll test them. ifconfig and netstat works correctly atleast. And about the caring, is rx/tx bytes so important that they can't use long long? I would care to see more than 4GB, and maybe some error in the counter at some point (Have you _ever_ seen that happen?) than only 4GB. And no, I didn't post this to be merged into the mainline kernel, just to let users know that there maybe is an option for seeing maximum 4GB. This has been working for me since, umm.. let's say 2.4.20. All the tools I've needed have worked. Markus