public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Saou  <thias@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net>
To: linux-kernel@vger.kernel.org
Subject: Wrong network usage reported by /proc
Date: Mon, 4 May 2009 17:14:08 +0200	[thread overview]
Message-ID: <20090504171408.3e13822c@python3.es.egwn.lan> (raw)

Hi,

I'm posting here as a last resort. I've got lots of heavily used RHEL5
servers (2.6.18 based) that are reporting all sorts of impossible
network usage values through /proc, leading to unrealistic snmp/cacti
graphs where the outgoing bandwidth used it higher than the physical
interface's maximum speed.

For some details and a test script which compares values from /proc
with values from tcpdump :
https://bugzilla.redhat.com/show_bug.cgi?id=489541

The values collected using tcpdump always seem realistic and match the
values seen on the remote network equipments. So my obvious conclusion
(but possibly wrong given my limited knowledge) is that something is
wrong in the kernel, since it's the one exposing the /proc interface.

I've reproduced what seems to be the same problem on recent kernels,
including the 2.6.27.21-170.2.56.fc10.x86_64 I'm running right now. The
simple python script available here allows to see it quite easily :
https://www.redhat.com/archives/rhelv5-list/2009-February/msg00166.html

 * I run the script on my Workstation, I have an FTP server enabled
 * I download a DVD ISO from a remote workstation : The values match
 * I start ping floods from remote workstations : The values reported
   by /proc are much higher than the ones reported by tcpdump. I used
   "ping -s 500 -f myworkstation" from two remote workstations

If there's anything flawed in my debugging, I'd love to have someone
point it out to me. TIA to anyone willing to have a look.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 10 (Cambridge) - Linux kernel
2.6.27.21-170.2.56.fc10.x86_64 Load : 0.39 0.30 0.34

             reply	other threads:[~2009-05-04 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 15:14 Matthias Saou [this message]
2009-05-04 17:53 ` Wrong network usage reported by /proc Eric Dumazet
2009-05-04 19:11   ` Matthias Saou
2009-05-05  5:04     ` Willy Tarreau
2009-05-05  5:22       ` Eric Dumazet
2009-05-05  5:50         ` Willy Tarreau
2009-05-05  8:09           ` Matthias Saou
2009-05-05  8:51             ` Eric Dumazet
2009-05-07 17:58               ` Matthias Saou
2009-05-05  4:46 ` Robert Hancock
2009-05-05  8:02   ` Matthias Saou

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=20090504171408.3e13822c@python3.es.egwn.lan \
    --to=thias@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net \
    --cc=linux-kernel@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