From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Unix trampoline?
Date: Sun, 25 Jan 2004 19:18:37 +0100 [thread overview]
Message-ID: <08ef01c3e36f$a7becc00$67844051@SOMA> (raw)
In-Reply-To: <6b2ae5458c847f6be69571ead32ceeca@terzarima.net>
> ... that's also when i
> discovered just how appalling Linux's scheduler actually is, and has
> been years. good source for a good sneer, anyhow.
it is truly frightening, particularily when you read comments like:
* 2002-01-04 New ultra-scalable O(1) scheduler by Ingo Molnar:
* hybrid priority-list and round-robin design with
* an array-switch method of distributing timeslices
* and per-CPU runqueues. Cleanups and useful suggestions
* by Davide Libenzi, preemptible kernel bits by Robert Love.
err, yes i've been delving through this stuff.
if you want a near death experience, read:
/usr/include/linux/list.h
next prev parent reply other threads:[~2004-01-25 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 12:45 a
2004-01-20 15:24 ` phillip stanley-marbell
2004-01-20 15:38 ` C H Forsyth
2004-01-25 7:22 ` Jack Johnson
2004-01-25 11:27 ` Bruce Ellis
2004-01-25 18:02 ` Charles Forsyth
2004-01-25 18:18 ` boyd, rounin [this message]
2004-01-20 16:29 ` Dan Cross
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='08ef01c3e36f$a7becc00$67844051@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).