public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: intermittant petabyte usage reported with broadcom nic
Date: Mon, 2 Apr 2007 11:43:19 +1000	[thread overview]
Message-ID: <20070402014319.GA8345@zip.com.au> (raw)

I take minute by minute snapshots of network traffic by sampling
/proc/net/dev and most of the time everything works fine. Occasionally
though I get petabyte byte traffic and corresponding packet traffic.

This happens on an AMD64, dual core smp box with Broadcom NetXtreme II
nics. The issue happens with both nics but at different times. The same
sampling code runs on p4 boxes with ht on and e1000 nics without issues
so I don't believe it's an issue with my code (famous last words :)
which just does an re to extract the data on a per-line basis and prints
it out. Still, I'll be adding code to log any big readings and hopefully
it'll happen again sooner rather then later.

There is no preemption involved and the kernel is a monolythic build of
2.6.19.[12] (there are two servers).

-- 
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby

             reply	other threads:[~2007-04-02  2:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02  1:43 CaT [this message]
2007-04-02  7:13 ` intermittant petabyte usage reported with broadcom nic Andrew Morton
2007-04-02  7:41   ` CaT
2007-04-02 10:31     ` Jean-Daniel Pauget
2007-04-15  0:20     ` Michael Chan
2007-04-16 19:10       ` Michael Chan
2007-04-16 23:43         ` CaT
2007-04-17 12:01           ` Jean-Daniel Pauget
2007-04-17 15:58           ` Roland Dreier
2007-05-22  1:15       ` Michael Chan
2007-04-12 22:52   ` CaT
2007-04-12 23:13     ` Andrew Morton
2007-04-12 23:18       ` Roland Dreier
2007-04-12 23:25         ` CaT
2007-04-12 23:15     ` Roland Dreier
2007-04-12 23:28     ` Roland Dreier
2007-04-13  1:15       ` Andi Kleen

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=20070402014319.GA8345@zip.com.au \
    --to=cat@zip.com.au \
    --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