From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Jens Gecius <jens@gecius.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3 smp irq balance
Date: Fri, 22 Aug 2003 02:12:33 +0200 [thread overview]
Message-ID: <20030822001233.GA32143@www.13thfloor.at> (raw)
In-Reply-To: <87vfsrq8vg.fsf@maniac.gecius.de>
On Thu, Aug 21, 2003 at 06:21:39PM +0200, Jens Gecius wrote:
> Arjan van de Ven <arjanv@redhat.com> writes:
>
> >> irqs seem not to be distributed between cpus, having one to handle all
> >> (even while building kernel on both cpus (according to gkrell), the
> >> numbers for the second cpu don't change.
> >
> > just install and run the irqbalance daemon from:
> > http://people.redhat.com/arjanv/irqbalance
>
> I did. Didn't change anything. The numbers are the same - the only
> CPU2 irq increasing is LOC. Any other hints?
I remember some strange case (somewhere around 2.4.18,
yes I know you are running 2.6.0 whatever) where I needed
to set the smp_affinity manually after boot, otherwise
the second cpu would not receive any interrupts on some
dual athlon system ...
echo ff >/proc/irq/xx/smp_affinity
did the trick, everything else was working as expected ...
just a weird idea, don't blame me if it actually works ;)
best,
Herbert
> --
> Tschoe, http://gecius.de/gpg-key.txt - Fingerprint:
> Jens 1AAB 67A2 1068 77CA 6B0A 41A4 18D4 A89B 28D0 F097
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-08-22 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 21:03 Jens Gecius
2003-08-21 12:21 ` Arjan van de Ven
2003-08-21 16:21 ` Jens Gecius
2003-08-22 0:12 ` Herbert Pötzl [this message]
2003-08-21 17:56 Pallipadi, Venkatesh
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=20030822001233.GA32143@www.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=jens@gecius.de \
--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®