From: Andrea Arcangeli <andrea@suse.de>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: multi-queue scheduler update
Date: Fri, 19 Jan 2001 02:35:02 +0100 [thread overview]
Message-ID: <20010119023502.G32087@athlon.random> (raw)
In-Reply-To: <20010119012616.D32087@athlon.random> <Pine.LNX.4.10.10101181956300.8128-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10101181956300.8128-100000@coffee.psychology.mcmaster.ca>; from hahn@coffee.psychology.mcmaster.ca on Thu, Jan 18, 2001 at 08:00:16PM -0500
On Thu, Jan 18, 2001 at 08:00:16PM -0500, Mark Hahn wrote:
> > > microseconds/yield
> > > # threads 2.2.16-22 2.4 2.4-multi-queue
> > > ------------ --------- -------- ---------------
> > > 16 18.740 4.603 1.455
> >
> > I remeber the O(1) scheduler from Davide Libenzi was beating the mainline O(N)
>
> isn't the normal case (as in "The Right Case to optimize")
> where there are close to zero runnable tasks? what realistic/sane
> scenarios have very large numbers of spinning threads? all server
> situations I can think of do not. not volanomark -loopback, surely!
This is why the numbers with 2/4/8 threads in the runqueue are the most
interesting ones 8)
Andrea
-
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 prev parent reply other threads:[~2001-01-19 1:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 23:53 multi-queue scheduler update Mike Kravetz
2001-01-19 0:26 ` Andrea Arcangeli
2001-01-19 0:51 ` [Lse-tech] " Andi Kleen
2001-01-19 1:14 ` John Clemens
2001-01-19 0:52 ` [Lse-tech] " Mike Kravetz
2001-01-19 1:30 ` Andrea Arcangeli
2001-01-19 1:34 ` Mike Kravetz
2001-01-19 20:49 ` Mike Kravetz
2001-01-19 21:51 ` Mike Kravetz
2001-01-19 22:03 ` Davide Libenzi
2001-01-19 22:18 ` Mike Kravetz
2001-01-19 23:24 ` Davide Libenzi
2001-01-19 1:39 ` Davide Libenzi
2001-01-19 16:06 ` David Lang
2001-01-19 1:00 ` Mark Hahn
2001-01-19 1:08 ` Andi Kleen
2001-01-19 1:23 ` Mike Kravetz
2001-01-19 1:38 ` Davide Libenzi
2001-01-19 1:35 ` Andrea Arcangeli [this message]
2001-01-19 1:48 ` Andi Kleen
2001-01-19 23:35 ` Mike Kravetz
2001-01-19 0:43 ` Gerhard Mack
2001-01-23 16:49 ` [Lse-tech] " Jun Nakajima
[not found] ` <LYR76657-1923-2001.01.23-08.54.49--mikek#sequent.com@lyris.sequent.com>
2001-01-23 17:08 ` Mike Kravetz
-- strict thread matches above, loose matches on Subject: below --
2001-01-21 17:49 Jesse Pollard
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=20010119023502.G32087@athlon.random \
--to=andrea@suse.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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 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.