mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: josh@toad.stack.nl
Cc: mikpe@csd.uu.se, linux-kernel@vger.kernel.org
Subject: Re: APIC error
Date: Thu, 15 May 2003 12:25:00 +0200 (CEST)	[thread overview]
Message-ID: <20030515.122500.35026542.rene.rebe@gmx.net> (raw)
In-Reply-To: <20030515120614.R94113@toad.stack.nl>

Hi,

On: Thu, 15 May 2003 12:09:38 +0200 (CEST),
    Jos Hulzink <josh@toad.stack.nl> wrote:
> > No load balancing of I/O interrupts since they will all be directed to
> > CPU 0 only. Unless your dual P5 is servicing a lot of interrupts, I doubt
> > it will make a noticeable difference.
> 
> On my Dual PII 333, KDE 3.1 runs fine with interrupts mapped to both CPUs,
> and performance is horrible when only CPU0 receives the interrupts.
> 
> Especially moving the timer interrupt to both CPUs makes difference like
> night and day.

Thanks for all your contributions ;-) But with noapic I also get APIC
errors from time to time (altough /etc/intrerrupts shows that the
XT-PIC is used). But anyway the box is not running very reliable in
both modes and processes seg-fault every now and then and sometimes
the box freezed. I'll get rid of the box I got for free and no longer
waste our time ... ;-)

> Jos

Sincerely,
  René Rebe

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene.rebe@gmx.net
http://www.rocklinux.org http://www.rocklinux.org/people/rene       
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene

      reply	other threads:[~2003-05-15 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 19:31 Rene Rebe
2003-05-14 12:55 ` mikpe
2003-05-14 20:18   ` Rene Rebe
2003-05-15  9:03     ` mikpe
2003-05-15 10:09       ` Jos Hulzink
2003-05-15 10:25         ` Rene Rebe [this message]

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=20030515.122500.35026542.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=josh@toad.stack.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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®