From: "Michael Chan" <mchan@broadcom.com>
To: "CaT" <cat@zip.com.au>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: intermittant petabyte usage reported with broadcom nic
Date: Sat, 14 Apr 2007 17:20:01 -0700 [thread overview]
Message-ID: <1176596401.5847.7.camel@dell> (raw)
In-Reply-To: <20070402074108.GB8345@zip.com.au>
On Mon, 2007-04-02 at 17:41 +1000, CaT wrote:
> On Mon, Apr 02, 2007 at 12:13:00AM -0700, Andrew Morton wrote:
> > On Mon, 2 Apr 2007 11:43:19 +1000 CaT <cat@zip.com.au> wrote:
> >
> > > 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.
> >
> > How frequently?
>
> I can count about 6 over the past month.
>
I did a quick test on a 64-bit kernel and did not see any problem with
the counters. I'll ask the lab to set up a longer term test and monitor
the counters for bogus values.
I also like Andi's idea of using change_page_attr() to isolate the
problem. I'll try to send you a debug patch in the next few days to try
that out. Thanks.
next prev parent reply other threads:[~2007-04-14 23:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 1:43 intermittant petabyte usage reported with broadcom nic CaT
2007-04-02 7:13 ` Andrew Morton
2007-04-02 7:41 ` CaT
2007-04-02 10:31 ` Jean-Daniel Pauget
2007-04-15 0:20 ` Michael Chan [this message]
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=1176596401.5847.7.camel@dell \
--to=mchan@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=cat@zip.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.