From: "David S. Miller" <davem@davemloft.net>
To: cw@f00f.org
Cc: Sebastian.Classen@freenet-ag.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: overflows in /proc/net/dev
Date: Thu, 18 Aug 2005 14:32:48 -0700 (PDT) [thread overview]
Message-ID: <20050818.143248.58283961.davem@davemloft.net> (raw)
In-Reply-To: <20050818163358.GA19554@taniwha.stupidest.org>
From: Chris Wedgwood <cw@f00f.org>
Date: Thu, 18 Aug 2005 09:33:58 -0700
> I thought the concensurs here was that because doing reliable atomic
> updates of 64-bit values isn't possible on some (most?) 32-bit
> architectures so we need additional locking to make this work which is
> undesirable? (It might even be a FAQ by now as this comes up fairly
> often).
That's correct.
next prev parent reply other threads:[~2005-08-18 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124350090.29902.8.camel@basti79.freenet-ag.de>
2005-08-18 16:33 ` overflows in /proc/net/dev Chris Wedgwood
2005-08-18 21:32 ` David S. Miller [this message]
2005-08-18 22:13 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050818.143248.58283961.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Sebastian.Classen@freenet-ag.de \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox