From: Jussi Laako <jussi.laako@kolumbus.fi>
To: Ed Tomlinson <tomlins@cam.org>
Cc: mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] improving O(1)-J9 in heavily threaded situations
Date: Mon, 04 Feb 2002 22:01:50 +0200 [thread overview]
Message-ID: <3C5EE8AE.1206EEEB@kolumbus.fi> (raw)
In-Reply-To: <Pine.LNX.4.33.0202040627001.22583-100000@localhost.localdomain> <20020204044055.EF0579251@oscar.casa.dyndns.org>
Ed Tomlinson wrote:
>
> One point that seems to get missed is that a group of java threads,
> posix threads or sometimes forked processes combine to make an
> application. Linux, at the scheduler level at least, does not have the
> ability to determine that all the tasks are really one application.
> Under light loads this makes no difference. When the load gets heavy
> having this ability helps here.
My application is very good example of this kind of application. I'm very
worried about the way new scheduler is beginning to behave. It's combination
of single processes with many threads and many processes with single
threads. And because it's kind of realtime application, _all_ processes and
threads are "interactive". CPU load is typically very high.
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
next prev parent reply other threads:[~2002-02-04 20:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0202040627001.22583-100000@localhost.localdomain>
2002-02-04 4:40 ` [PATCH] improving O(1)-J9 in heavily threaded situations Ed Tomlinson
2002-02-04 12:30 ` Ingo Molnar
2002-02-04 12:36 ` Ingo Molnar
2002-02-04 10:47 ` Arjan van de Ven
2002-02-04 14:09 ` Ingo Molnar
2002-02-04 12:18 ` Ed Tomlinson
2002-02-04 20:01 ` Jussi Laako [this message]
2002-02-04 22:06 ` Ingo Molnar
2002-02-04 22:56 ` Jussi Laako
2002-02-05 0:56 ` Ingo Molnar
2002-02-04 23:32 ` Jussi Laako
2002-02-05 1:34 ` Ingo Molnar
2002-02-04 22:24 ` Bill Davidsen
2002-02-04 12:32 Ed Tomlinson
2002-02-04 12:33 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2002-02-03 6:00 Ed Tomlinson
2002-02-02 15:50 Ed Tomlinson
2002-02-03 11:32 ` Ingo Molnar
2002-02-03 15:46 ` Ed Tomlinson
2002-02-04 0:46 ` Ingo Molnar
2002-02-04 19:52 ` Jussi Laako
2002-02-05 0:59 ` Ingo Molnar
2002-02-04 23:36 ` Jussi Laako
2002-02-05 1:37 ` Ingo Molnar
2002-02-06 0:43 ` Jussi Laako
2002-02-06 12:37 ` Ingo Molnar
2002-02-07 1:10 ` Jussi Laako
2002-02-07 22:28 ` Ingo Molnar
2002-02-10 15:00 ` Jussi Laako
2002-02-05 1:41 ` Ingo Molnar
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=3C5EE8AE.1206EEEB@kolumbus.fi \
--to=jussi.laako@kolumbus.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tomlins@cam.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