From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] O(1) MQ scheduler J9 patch for IA64
Date: Sat, 02 Feb 2002 00:21:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805981@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805977@msgid-missing>
On Fri, 1 Feb 2002 15:45:32 +0100 (MET),
Erich Focht <efocht@ess.nec.de> wrote:
>please find attached a patch which aplies to
>
>linux-2.4.17 + kdb_common + ia64_patch + kdb_ia64 + sched-O1-2.4.17-J9.patch
>
>I had to add a function smp_call_function_nowait which sends an IPI and
>returns immediately in order to get rid of a IA64-specific race condition
>when the mmu_context wraps around. Now it makes a very stable and fast
>impression, interactive work is even possible while doing a "hackbench
>55" and ping flooding the machine... Tested on 2 CPU BigSur, 4 CPU LION,
>16 CPU AzusA.
Why is there a global change of current->processor to current->cpu?
That has knock on effects because #define cpu and references to that
macro also have to be changed. I don't see any benefit.
next prev parent reply other threads:[~2002-02-02 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 14:45 [Linux-ia64] O(1) MQ scheduler J9 patch for IA64 Erich Focht
2002-02-02 0:21 ` Keith Owens [this message]
2002-02-04 17:21 ` Erich Focht
2002-02-04 19:22 ` 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=marc-linux-ia64-105590698805981@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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