From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ERR in /proc/interrupts
Date: Thu, 18 Jan 2001 16:21:58 -0600 [thread overview]
Message-ID: <20010118222204Z135868-404+1119@vger.kernel.org> (raw)
In-Reply-To: <20010118161000.A3487@mediaone.net>
In-Reply-To: <001c01c08199$387205f0$067039c3@cintasverdes> <001c01c08199$387205f0$067039c3@cintasverdes> from Jorge Boncompte (DTI2) on 01/18/2001 15:54
** Reply to message from Tim Walberg <tewalberg@mediaone.net> on Thu, 18 Jan
2001 16:10:00 -0600
> A quick perusal of the 2.2.18 source code (I don't have
> a copy of 2.4.x handy) shows that it's directly
> related to the number of IPIs (inter-processor
> interrupts) the system has taken. I'm not real
> sure under what conditions this occurs, but it's
> someplace to start...
I thought one reason why IPI's were used was to synchronize the CPUs for a
cache flush. That hardly sounds like an error condition to me.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please direct the reply to the mailing list only. Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 21:54 Jorge Boncompte (DTI2)
2001-01-18 22:10 ` Tim Walberg
2001-01-18 22:31 ` Jorge Boncompte (DTI2)
2001-01-18 22:41 ` Timur Tabi
2001-01-18 22:58 ` Jorge Boncompte (DTI2)
2001-01-18 22:21 ` Timur Tabi [this message]
2003-09-30 9:39 Andreas Schwarz
2003-09-30 10:16 ` Christian
2003-09-30 10:34 ` Andreas Schwarz
2003-09-30 17:54 ` Andreas Schwarz
2003-09-30 10:45 ` Raj
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=20010118222204Z135868-404+1119@vger.kernel.org \
--to=ttabi@interactivesi.com \
--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®