public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Chris Meadors <clubneon@hereintown.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual XEON - >>SLOW<< on SMP
Date: Thu, 2 Nov 2000 18:39:30 -0500	[thread overview]
Message-ID: <20001102183930.A17064@animx.eu.org> (raw)
In-Reply-To: <m3bsvy2qlb.fsf@otr.mynet.cygnus.com> <Pine.LNX.4.21.0011021334170.83-100000@rc.priv.hereintown.net>
In-Reply-To: <Pine.LNX.4.21.0011021334170.83-100000@rc.priv.hereintown.net>; from Chris Meadors on Thu, Nov 02, 2000 at 01:38:18PM -0500

> > I'm seeing this as well, but only with PIII Xeon systems, not PII
> > Xeon.  Every single timer interrupt on any CPU is accompanied by a NMI
> > and LOC increment on every CPU.
> > 
> >            CPU0       CPU1       
> >   0:     146727     153389    IO-APIC-edge  timer
> > [...]
> > NMI:     300035     300035 
> > LOC:     300028     300028 
> 
> You mean that isn't supposed to happen?
> 
>            CPU0       CPU1
>   0:    8480192    7786028    IO-APIC-edge  timer
>   1:          3          1    IO-APIC-edge  keyboard
>   2:          0          0          XT-PIC  cascade
>   8:          0          0    IO-APIC-edge  rtc
>  13:          0          0          XT-PIC  fpu
>  23:     188915     191259   IO-APIC-level  eth0
>  28:         16         14   IO-APIC-level  sym53c8xx
>  29:      33655      33665   IO-APIC-level  sym53c8xx
>  30:          0          0   IO-APIC-level  es1371
> NMI:   16266140   16266140
> LOC:   16266123   16266122
> ERR:          0
> 
> This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
> chipset.

[wakko@gohan:/home/wakko] cat /proc/interrupts 
           CPU0       CPU1       
  0:   15276613   18358687    IO-APIC-edge  timer
  1:        391        455    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  4:          1          0    IO-APIC-edge  serial
 13:          1          0          XT-PIC  fpu
 14:       3013       2422    IO-APIC-edge  ide0
 16:     179450     191589   IO-APIC-level  eth0
 17:         22         23   IO-APIC-level  aic7xxx
 18:      17254      15655   IO-APIC-level  es1371
 19:         11         10   IO-APIC-level  aic7xxx
NMI:   33635184   33635184 
LOC:   33636726   33636725 
ERR:          0
[wakko@gohan:/home/wakko] cat /proc/mtrr 

I noticed it was a tad slow, but I figured it was the fact it was a netboot
machine.  It's a dual ppro 200 192mb ram.
                         
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
-
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/

  parent reply	other threads:[~2000-11-02 23:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 13:50 Dual XEON - >>SLOW<< on SMP Dr. David Gilbert
2000-11-02 13:56 ` kernel
2000-11-02 14:02   ` Richard B. Johnson
2000-11-02 18:09     ` Ulrich Drepper
2000-11-02 18:23       ` Maciej W. Rozycki
2000-11-02 18:26       ` Matti Aarnio
2000-11-02 18:38       ` Chris Meadors
2000-11-02 18:40         ` Richard B. Johnson
2000-11-02 23:39         ` Wakko Warner [this message]
2000-11-07 22:02         ` Dr. Kelsey Hudson
2000-11-07 22:10           ` Jan-Benedict Glaw
2000-11-07 22:16             ` kernel
2000-11-07 22:31           ` Richard B. Johnson
2000-11-07 22:41             ` Keith Owens
2000-11-07 22:55               ` Richard B. Johnson
2000-11-07 23:03                 ` Jeff V. Merkey
2000-11-08 14:28                   ` Richard B. Johnson
2000-11-08 19:17                     ` Jeff V. Merkey
2000-11-11 19:26                   ` Marc Lehmann
2000-11-13  6:22                     ` Jeff V. Merkey
2000-11-13  8:41                       ` James A. Sutherland
2000-11-13 11:51                       ` Marc Lehmann
2000-11-07 22:48             ` J . A . Magallon
2000-11-02 14:10   ` Tigran Aivazian
2000-11-02 17:39     ` Dr. David Gilbert
2000-11-03  0:04       ` bert hubert
2000-11-03 16:13         ` Ricky Beam

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=20001102183930.A17064@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=clubneon@hereintown.net \
    --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