From: Robert Love <rml@tech9.net>
To: Jussi Laako <jussi.laako@kolumbus.fi>
Cc: Mike Kravetz <kravetz@us.ibm.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: O(1) scheduler gives big boost to tbench 192
Date: 08 May 2002 09:31:39 -0700 [thread overview]
Message-ID: <1020875500.2078.117.camel@bigsur> (raw)
In-Reply-To: <3CD94582.DE18AB99@kolumbus.fi>
On Wed, 2002-05-08 at 08:34, Jussi Laako wrote:
> Mike Kravetz wrote:
> >
> > I'd really like to know if there are any real workloads that
> > benefited from this feature, rather than just some benchmark.
>
> Maybe this is the reason why O(1) scheduler has big latencies with
> pthread_cond_*() functions which original scheduler doesn't have?
> I think I tracked the problem down to try_to_wake_up(), but I was unable to
> fix it.
Ah this could be the same case. I just looked into the definition of
the conditional variable pthread stuff and it looks like it _could_ be
implemented using pipes but I do not see why it would per se. If it
does not use pipes, then this sync issue is not at hand (only the pipe
code passed 1 for the sync flag).
If it does not use pipes, we could have another problem - but I doubt
it. Maybe the benchmark is just another case where it shows worse
performance due to some attribute of the scheduler or load balancer?
Robert Love
next prev parent reply other threads:[~2002-05-08 16:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 13:38 O(1) scheduler gives big boost to tbench 192 rwhron
2002-05-03 20:29 ` Gerrit Huizenga
2002-05-04 8:13 ` Andrea Arcangeli
2002-05-07 22:13 ` Mike Kravetz
2002-05-07 22:44 ` Alan Cox
2002-05-07 22:43 ` Mike Kravetz
2002-05-07 23:39 ` Robert Love
2002-05-07 23:48 ` Mike Kravetz
2002-05-08 15:34 ` Jussi Laako
2002-05-08 16:31 ` Robert Love [this message]
2002-05-08 17:02 ` Mike Kravetz
2002-05-09 0:26 ` Jussi Laako
2002-05-08 8:50 ` Andrea Arcangeli
2002-05-09 23:18 ` Mike Kravetz
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 12:46 rwhron
2002-05-08 16:39 Bill Davidsen
2002-05-06 8:20 rwhron
2002-05-06 16:42 ` Andrea Arcangeli
2002-05-03 16:37 John Hawkes
2002-05-02 21:36 rwhron
2002-05-03 0:09 ` Gerrit Huizenga
2002-05-02 23:17 ` J.A. Magallon
2002-05-03 0:14 ` Alan Cox
2002-05-03 1:08 ` Gerrit Huizenga
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=1020875500.2078.117.camel@bigsur \
--to=rml@tech9.net \
--cc=jussi.laako@kolumbus.fi \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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