From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: hahn@coffee.psychology.mcmaster.ca, linux-kernel@vger.kernel.org
Subject: Re: multi-queue scheduler update
Date: Sun, 21 Jan 2001 11:49:52 -0600 (CST) [thread overview]
Message-ID: <200101211749.LAA20104@tomcat.admin.navo.hpc.mil> (raw)
Mark Hahn <hahn@coffee.psychology.mcmaster.ca>:
>
> > > 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!
How about massively parallel compute jobs when synchronizing.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
-
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:[~2001-01-21 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 17:49 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 0:51 [Lse-tech] Re: multi-queue scheduler update Andi Kleen
2001-01-19 1:14 ` John Clemens
2001-01-18 23:53 Mike Kravetz
2001-01-19 0:26 ` Andrea Arcangeli
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
2001-01-19 1:48 ` Andi Kleen
2001-01-19 23:35 ` Mike Kravetz
2001-01-19 0:43 ` Gerhard Mack
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=200101211749.LAA20104@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox