kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Computing
Date: Sun, 17 Apr 2011 11:39:06 +0700	[thread overview]
Message-ID: <BANLkTi=7UCjMWJcDPmM7Kg1M8O8QsPwtZA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin-ucmi-13OdpAViS2RLYKivtgp7Q@mail.gmail.com>

On Sun, Apr 17, 2011 at 02:04, Rigved Rakshit <r.phate@gmail.com> wrote:
> 1. Process A has just been scheduled to execute for the first time on
> machine A.
> 2. I send a suspend signal to Process A, mostly a SIGSTOP.
> 3. Then I copy Process A's PCB to machine B.
> 4. On machine B, I send the continue signal to Process A, mostly a SIGCONT.
> 5. Whenever Process A needs user input or needs to output something, I cause
> a trap, mostly with a SIGTRAP (or I could use SIGSTOP here again). I
> transfer this I/O request to machine A and let the user interact. I send the
> interaction back to Process A on machine B. I resume Process A on machine B.
> 6. I continue these steps till Process A has completed execution.

Sounds like just what MOSIX, OpenSSI or Kerrighed already do....

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2011-04-17  4:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 19:04 Distributed Computing Rigved Rakshit
2011-04-17  4:39 ` Mulyadi Santosa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-18 21:12 Rigved Rakshit

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='BANLkTi=7UCjMWJcDPmM7Kg1M8O8QsPwtZA@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).