From: Sam Mason <mason@f2s.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 21:14:17 +0100 [thread overview]
Message-ID: <20020717201417.GA9546@sam.home.net> (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:
>Can you point out specific (real-life) workloads where this
>would be advantegous?
It's mainly used for programs that needs lots of processing power
chucked at a specific problem, the problem is first broken down into
several small pieces and each part is sent off to a different
processor. When each piece has been processed, they are all
recombined and the rest of the calculation is continued. The problem
with this is that if any one of the pieces is delayed, all the
processors will be idle waiting for the interrupted piece to be
processed, before they can process the next set of pieces.
Sam
next prev parent reply other threads:[~2002-07-17 19:58 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
2002-07-17 20:14 ` Sam Mason [this message]
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=20020717201417.GA9546@sam.home.net \
--to=mason@f2s.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