mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Axel Weiß" <aweiss@informatik.hu-berlin.de>
Cc: John Que <qwejohn@hotmail.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: NIC inerrupt
Date: Tue, 20 Apr 2004 11:41:08 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0404201138380.568@chaos> (raw)
In-Reply-To: <200404201604.17238.aweiss@informatik.hu-berlin.de>

On Tue, 20 Apr 2004, Axel [iso-8859-15] Weiß wrote:

> Am Montag, 19. April 2004 14:46 schrieb John Que:
> > Hello,
> >
> > I want to count the number of times I reach an NIC receive
> > interrupt.
> >
> > I added a global static variable of type int , and initialized
> > it to 0 ; each time I am in the rx_interrupt of the card I incerement
> > it by one;
> > I got large , non sensible numbers after one or two seconds;
> >
> > So  for debug I added printk each time I increment it in rx_interrupt.
> >
> > What I see is that there are  unreasonable jumps in the number
> >
> > for instance , it inceremnts sequntially from 1 to 80,then jums to 4500,
> > increments a little sequentially to 4580, and the jums again to
> > 11000 ;
> >
> > Is it got to do with it that this is in interrupt?
> > Any idea what it can be ?
> >
> >
> > (I also tried to declare it as static in the rx_interrupt method
> > and the same happened)
>
> Probably you didn't declare your count variable 'volatile'?
>
> Axel
>
> --
> Humboldt-Universität zu Berlin
> Institut für Informatik
> Signalverarbeitung und Mustererkennung
> Dipl.-Inf. Axel Weiß
> Rudower Chaussee 25
> 12489 Berlin-Adlershof
> +49-30-2093-3050

How about `cat /proc/interrupts`. That should tell him how
many interrupts the NIC got..

           CPU0
  0:     123073    IO-APIC-edge  timer
  1:       1131    IO-APIC-edge  keyboard
  2:          0          XT-PIC  cascade
 17:      18550   IO-APIC-level  BusLogic BT-958
 18:      69272   IO-APIC-level  eth0	<----------
NMI:          0
LOC:     123029
ERR:          0
MIS:          0

Do the simple stuff first. Only get compilcated if necessary.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5596.77 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-04-20 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 12:46 John Que
2004-04-19 12:54 ` Denis Vlasenko
2004-04-19 14:40 ` Bart Samwel
2004-04-20 14:04 ` Axel Weiß
2004-04-20 15:41   ` Richard B. Johnson [this message]
2004-04-19 15:01 John Que

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=Pine.LNX.4.53.0404201138380.568@chaos \
    --to=root@chaos.analogic.com \
    --cc=aweiss@informatik.hu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qwejohn@hotmail.com \
    /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®