From: "Anonymous" <anonymos@micron.net>
To: <linux-kernel@vger.kernel.org>
Subject: 1.2.45 Linux Scheduler
Date: Tue, 31 Oct 2000 20:12:12 -0800 [thread overview]
Message-ID: <004d01c043b9$e9cfe2e0$53b613d1@micron.net> (raw)
In the Linux scheduler they use a circular queue implementation with round
robin. What is the advantage of this over just using a normal queue with a
back and front. Also does anyone know what a test plan for such a design
would even begin to look like. This is a project for a proposal going around
in my neighborhood and I am wondering why in the world someone would want to
modify the Linux scheduler to this extent.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-01 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 4:12 Anonymous [this message]
2000-11-01 17:50 ` 1.2.45 Linux Scheduler George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2000-11-01 13:27 Jesse Pollard
2000-11-01 14:06 ` Davide Libenzi
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='004d01c043b9$e9cfe2e0$53b613d1@micron.net' \
--to=anonymos@micron.net \
--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