From: Manfred Spraul <manfred@colorfullife.com>
To: mingo@elte.hu
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [sched] [patch] migration-fixes-2.5.3-pre2-A1
Date: Mon, 21 Jan 2002 16:40:48 +0100 [thread overview]
Message-ID: <3C4C3680.39DD06D8@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201202254440.14434-100000@localhost.localdomain>
Ingo Molnar wrote:
>
> So i think the P6 documentation is a pessimisation of the true situation,
> and that we can very well have multiple interrupts on the same priority
> level even on older APICs - as long as the local timer interrupt is not
> amongst them.
>
You are right.
I tried to reproduce it (force cpu1 to priority 15, send 4 ipis to
priority 14 from cpu0, check that all arrive), and it seems that the
pIII doesn't drop ipi messages.
--
Manfred
next prev parent reply other threads:[~2002-01-21 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 14:26 [sched] [patch] migration-fixes-2.5.3-pre2-A1 Manfred Spraul
2002-01-20 21:59 ` Ingo Molnar
2002-01-21 15:40 ` Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-20 13:36 Ingo Molnar
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=3C4C3680.39DD06D8@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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