public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: shreenivasa H V <shreenihv@usa.net>, linux-kernel@vger.kernel.org
Subject: Re: Gang Scheduling in linux
Date: Wed, 17 Jul 2002 10:47:16 -0700	[thread overview]
Message-ID: <20020717174716.GI1096@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207181930170.32666-100000@localhost.localdomain>

On Thu, Jul 18, 2002 at 07:40:19PM +0200, Ingo Molnar wrote:
> you are right in that the Linux scheduler does not enable classic
> gang-scheduling: where multiple processes are scheduled 'at once' on
> multiple CPUs. Can you point out specific (real-life) workloads where this
> would be advantegous? Some testcode would be the best form of expressing
> this. Pretty much any job that uses sane (kernel-based or kernel-helped)
> synchronization should see good throughput.

I will not advocate it myself. I only remembered the definition.


Cheers,
Bill

  reply	other threads:[~2002-07-17 17:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 22:54 Gang Scheduling in linux shreenivasa H V
2002-07-18 16:21 ` Ingo Molnar
2002-07-17 17:40   ` William Lee Irwin III
2002-07-18 17:40   ` Ingo Molnar
2002-07-17 17:47     ` William Lee Irwin III [this message]
2002-07-17 20:14     ` Sam Mason
2002-07-18 20:08       ` Ingo Molnar
2002-07-17 20:39         ` Sam Mason
2002-07-18 20:32           ` Ingo Molnar
2002-07-17 21:24             ` Sam Mason
2002-07-18 12:43             ` Jean Wolter
2002-07-19 15:05     ` Hubertus Franke
2002-07-20 16:59       ` Ingo Molnar
2002-07-19 19:25         ` Hubertus Franke
2002-07-19 22:05           ` Richard Gooch
2002-07-22 19:52             ` Hubertus Franke

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=20020717174716.GI1096@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shreenihv@usa.net \
    /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