From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Subject: [patch] sched-2.5.24-D3, batch/idle priority scheduling, SCHED_BATCH
Date: Mon, 1 Jul 2002 11:45:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0207011137330.4167-100000@e2> (raw)
the sched-2.5.24-D3 patch is my current scheduler tree against 2.5.24,
which also includes the latest version of SCHED_BATCH support:
http://redhat.com/~mingo/O(1)-scheduler/sched-2.5.24-D3
the setbatch utility can be found at:
http://redhat.com/~mingo/O(1)-scheduler/setbatch.c
Changes relative to the previous SCHED_BATCH patch:
- fix signal delivery - call the 'kick batch processes' code on UP as
well.
- simplify and speed up the batch queue handling code: the expired/active
queues are merged into a single queue. If a SCHED_BATCH process uses up
all its timeslices then it is queued to the tail of the batch-queue -
otherwise it's queued to the head of the batch-queue. This simplifies
the load-balancer as well.
- add 'default context-switch locking' if prepare_arch_schedule() is not
defined. The majority of architectures thus do not have to define the
context-switch locking macros.
bug reports, success reports, comments, suggestions are welcome,
Ingo
next reply other threads:[~2002-07-01 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 9:45 Ingo Molnar [this message]
2002-07-10 2:30 ` O(1) batch scheduler Kevin O'Connor
2002-07-11 6:27 ` Ingo Molnar
2002-07-11 6:32 ` Ingo Molnar
2002-07-11 7:05 ` [patch] " Ingo Molnar
2002-07-11 4:41 ` Kevin O'Connor
2002-07-06 18:18 [patch] sched-2.5.24-D3, batch/idle priority scheduling, SCHED_BATCH oleg
2002-07-10 19:38 ` Ingo Molnar
2002-07-10 19:46 ` Ingo Molnar
2002-07-11 7:15 ` Ingo Molnar
2002-07-14 12:29 ` Pavel Machek
2002-07-15 16:31 ` Robert Love
2002-07-18 6:46 ` Ingo Molnar
2002-07-10 22:34 Oleg Nesterov
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=Pine.LNX.4.44.0207011137330.4167-100000@e2 \
--to=mingo@elte.hu \
--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®