From: Hubertus Franke <frankeh@watson.ibm.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Ingo Molnar <mingo@elte.hu>, shreenivasa H V <shreenihv@usa.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: Gang Scheduling in linux
Date: Mon, 22 Jul 2002 15:52:45 -0400 [thread overview]
Message-ID: <200207221552.45522.frankeh@watson.ibm.com> (raw)
In-Reply-To: <200207192205.g6JM5TR12776@vindaloo.ras.ucalgary.ca>
On Friday 19 July 2002 06:05 pm, Richard Gooch wrote:
> Hubertus Franke writes:
> > On a single SMP I could imagine for instance for parallel reendering
> > or similar tightly integrated parallel programs that need data
> > synchronization. Most of these apps assume a tightly coupled
> > non-virtual resource, i.e., scheduling of tasks is aligned.
> >
> > SGI used to have that stuff in their base kernel. Read a paper about
> > this some years ago. Again, at the beginning I'd go with a user
> > level scheduler approach that certainly would satisfy national labs
> > etc. Most of the cluster schedulers, like PBS and LoadLeveler etc.,
> > already provide that functionality.
>
> A completely user-level solution may have some disadvantages, though,
> such as delays in scheduling on/off (say if some daemon is used to
> scan the process list). Perhaps we could add a small hack to the
> scheduler such that when a task is about to be scheduled off, a signal
> can be sent to a designated pid? Similarly, when a task is scheduled
> on, another signal may be sent. An application that wanted to have
> gang scheduling could then make use of this to STOP/CONT threads.
>
> Regards,
>
> Richard....
> Permanent: rgooch@atnf.csiro.au
> Current: rgooch@ras.ucalgary.ca
I am glad you brought this up. I'd love to have a generic callback for this.
AIX used/has a process change handler that is being called on start/exit.
In Linux, this idea could be done through a generic hook settable through a
module... that should be sufficient and would allow for other stuff to
be handled as well. For instance in the presence of fast user level
communication (e.g. user mapped windows to myrinet the current
process could be marked in the communication adapter).
Just thinking loud.
--
-- Hubertus Franke (frankeh@watson.ibm.com)
prev parent reply other threads:[~2002-07-22 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 22:54 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
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 [this message]
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=200207221552.45522.frankeh@watson.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rgooch@ras.ucalgary.ca \
--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
Powered by JetHome