From: Ingo Molnar <mingo@elte.hu>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: O(1) scheduler "complex" macros
Date: Wed, 10 Jul 2002 19:30:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905748@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905752@msgid-missing>
the best solution might be to just lock the 'next' task - this needs a new
per-task irq-safe spinlock, to avoid deadlocks. This way whenever a task
is in the middle of a context-switch it cannot be scheduled on another
CPU.
in fact this solution simplifies things - only two per-arch macros are
needed. I've done this in my current 2.5.25 tree:
http://redhat.com/~mingo/O(1)-scheduler/sched-2.5.25-A4
check out the sparc64 changes for the 'complex' locking scenario - it's
untested, please give it a go on ia64, does that solve your problems? x86
is tested and works just fine.
Ingo
next prev parent reply other threads:[~2002-07-10 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 9:05 [Linux-ia64] Re: O(1) scheduler "complex" macros Erich Focht
2002-07-10 12:34 ` Erich Focht
2002-07-10 18:31 ` Ingo Molnar
2002-07-10 19:30 ` Ingo Molnar [this message]
2002-07-11 9:25 ` Erich Focht
2002-07-11 9:31 ` Ingo Molnar
2002-07-11 9:39 ` Ingo Molnar
2002-07-11 9:52 ` Ingo Molnar
2002-07-12 12:39 ` Pavel Machek
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-105590701905748@msgid-missing \
--to=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.