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:40:36 -0700 [thread overview]
Message-ID: <20020717174036.GG1096@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207181818300.29003-100000@localhost.localdomain>
On Thu, Jul 18, 2002 at 06:21:41PM +0200, Ingo Molnar wrote:
> yes - the 'synchronous wakeup' feature is a form of gang scheduling. It in
> essence uses real process-communication information to migrate 'related'
> tasks to the same CPU. So it's automatic, no need to declare processes to
> be part of a 'gang' in some formal (and thus fundamentally imperfect) way.
> (another form of 'gang scheduling' can be achieved by binding the 'parent'
> process to a single CPU - all children will be bound to that CPU as well.)
Hit #1 on google.com: http://www.sw.nec.co.jp/hpc/sx-e/sx-world/no23/en10.pdf
[SX-5 SERIES TECHNICAL HIGHLIGHTS]
Overview of Gang Scheduling
Koichi Nakanishi,
Senior Manager
Koji Suzuki,
Assistant Manager
4th Development Department, 1st Computers Software Division, Computers
Software Operations Unit, NEC Corporation
SX WORLD
Autumn 1998 No.23 Special Issue
[...]
The Gang scheduling function has the func-
tion of simultaneously allocating the required
number of CPUs when scheduling parallel
programs, and allows you to obtain almost
the same performance when multiple parallel
programs are simultaneously executing, as if
the programs were running alone.
I have approximately zero interest in this myself, but something seemed
off about the definition of gang scheduling being used in the post.
Cheers,
Bill
next prev parent reply other threads:[~2002-07-17 17:37 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 [this message]
2002-07-18 17:40 ` Ingo Molnar
2002-07-17 17:47 ` William Lee Irwin III
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=20020717174036.GG1096@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