From: Shane Nay <shane@minirl.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tyan S2466 MPX integrated ethernet interrupt happy
Date: Sat, 23 Mar 2002 05:45:24 -0800 [thread overview]
Message-ID: <20020323134429Z293129-616+181@vger.kernel.org> (raw)
In-Reply-To: <200203222229.g2MMT4t30679@zeus.kernel.org> <3C9BE024.B2A5ED0F@zip.com.au>
> > So, approximately 8.5 million ethernet interrupts. The system is
> > noticably slower when streaming ethernet data, and it's sucking
> > up a lot more processing time than on my other much slower other
> > box. This box is running a stock 2.4.18 kernel from kernel.org
> > (i.e. no custom hacks). It's running 2 1800+ XPs.
>
> That all looks normal. Could you be more specific about
> the performance problems? How much slower? Output from
> `top' and `ps'? Any nasty messages in the system log?
No nasties in the syslog. System usage from top averages 50% per
CPU. (By system I mean kernel usage, bounces between 70 and 30 per
CPU)
> Looking at the ethernet driver won't help, I expect - it's
> as efficient as most any other driver. If there is a problem,
> it lies elsewhere...
Gotcha, yes that could definetly be. This was extraordinarily
unscientific. I was thinking maybe someone had seen something else
like this on this platform. So, I'll write a test that isolates
ethernet from other stuff like ide performance, etc.
> A kernel profile would be illuminating. Build the kernel with as
> few modules as possible, boot the machine with `profile=1' and play
> with readprofile.
Will do when I return.
Thanks,
Shane Nay.
(Someone else noted their /proc/interrupts for the same machine, but
my box had only been up for 1.5 hours :)
next prev parent reply other threads:[~2002-03-23 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 22:29 Shane Nay
2002-03-23 1:53 ` Andrew Morton
2002-03-23 13:45 ` Shane Nay [this message]
2002-03-23 3:22 ` Bill Davidsen
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=20020323134429Z293129-616+181@vger.kernel.org \
--to=shane@minirl.com \
--cc=akpm@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
all inboxes | Powered by JetHome®