public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Samwel <bart@samwel.tk>
To: John Que <qwejohn@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NIC inerrupt
Date: Mon, 19 Apr 2004 16:40:08 +0200	[thread overview]
Message-ID: <4083E4C8.4090202@samwel.tk> (raw)
In-Reply-To: <BAY14-F34eqdGSyMp690005e9f6@hotmail.com>



John Que wrote:
> 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 ?

You're probably reading the kernel output from syslog. Syslog 
periodically reads out the printks from the kernel. With the amount of 
printks you're doing you are probably printing info for about 4500 
interrupts between every time syslog checks for new kernel output, while 
the kernel buffer that is used to store this information can only handle 
   enough data for 80 interrupts.

--Bart

  parent reply	other threads:[~2004-04-19 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 12:46 NIC inerrupt John Que
2004-04-19 12:54 ` Denis Vlasenko
2004-04-19 14:40 ` Bart Samwel [this message]
2004-04-20 14:04 ` Axel Weiß
2004-04-20 15:41   ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
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=4083E4C8.4090202@samwel.tk \
    --to=bart@samwel.tk \
    --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