mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <joerg.beyer@email.de>
To: joerg.beyer@email.de, "MattiAarnio" <matti.aarnio@zmailer.org>
Cc: linux-kernel@vger.kernel.org, "ZwaneMwaikambo" <zwane@linuxpower.ca>
Subject: Re: Re: big IRQ latencies, was:  <no subject>
Date: Sun, 25 Aug 2002 15:42:28 +0200	[thread overview]
Message-ID: <200208251342.g7PDgSX20335@mailgate5.cinetic.de> (raw)

Matti Aarnio <matti.aarnio@zmailer.org> schrieb am 25.08.02 15:18:07:
> On Sun, Aug 25, 2002 at 02:38:59PM +0200, joerg.beyer@email.de wrote:
> > Zwane Mwaikambo <zwane@linuxpower.ca> schrieb am 25.08.02 14:10:12:
> > > On Sun, 25 Aug 2002 joerg.beyer@email.de wrote:
> > ...
> > > That should fix your slowdown during untarring/disk access, as for your 
> > > NIC problem looks like you might be having a receive FIFO overflow, so 
> > > perhaps the card stops processing incoming packets? I have no clue, 
> > 
> > maybe this helps: outgoing transfer (from the laptop to some
> > other machine) is reasonable fast: I could copy gig's of data
> > away, but not to the machine. I asume sending away makes not
> > so heavy use of IRQ's, right?
> 
> A laptop, you say ?   And network reception is jamming while

yes a laptop.

> there is high disk-write activity ?

nope - no other disk activity except the scp I used to
copy a file over the net. 
 
>   /sbin/hdparam -v /dev/hda
> 
> /dev/hda:
>  multcount    = 16 (on)
>  I/O support  =  1 (32-bit)  <-----  ??
>  unmaskirq    =  1 (on)      <-----  ??
>  using_dma    =  1 (on)      <-----  ??
>  keepsettings =  1 (on)      <-----  ??
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
> 

I set the values as you suggested, but it made no difference:

joerg@laptop> scp othermachione:1gig_file /tmp

it take ~ 1/2 minute for 1 gig and gives a lot of errors
on the nic:

eth0      Protokoll:Ethernet  Hardware Adresse 00:07:CA:00:AC:A3  
          inet Adresse:10.0.0.30  Bcast:10.255.255.255  Maske:255.0.0.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:875 errors:6440 dropped:263 overruns:6440 frame:0
          TX packets:897 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:100 
          RX bytes:1234333 (1.1 Mb)  TX bytes:79498 (77.6 Kb)
          Interrupt:10 Basisadresse:0xf000 

along with > 300 entries in /var/log/messages like this:

kernel: eth0: Too much work at interrupt, IntrStatus=0x0040

could anybody explain to me, why there is "Too much work at interrupt"?
and what I could do about it?

    Joerg


                 reply	other threads:[~2002-08-25 13:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200208251342.g7PDgSX20335@mailgate5.cinetic.de \
    --to=joerg.beyer@email.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=zwane@linuxpower.ca \
    /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®