From: r.phate@gmail.com (Rigved Rakshit)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Computing
Date: Sun, 17 Apr 2011 00:34:21 +0530 [thread overview]
Message-ID: <BANLkTin-ucmi-13OdpAViS2RLYKivtgp7Q@mail.gmail.com> (raw)
Hi,
I need help with a couple of things. I will ask them one by one.
I want to "catch" a newly started process, transfer it to a remote machine,
execute this process on the remote machine and then return the result to the
original machine. Can anyone guide me with regard to this? Maybe if anyone
could point me to the relevant documentation, then also that would be great.
One possible method that I thought of is something like this:
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.
I do not know how to do any of these (but I do know how to transfer files
between two computer using rsync and how to send messages using TCP/UDP). If
someone could point me in the right direction, it would be of great help to
me.
Thanks in advance.
Regards,
Rigved Rakshit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110417/57fb85fb/attachment.html
next reply other threads:[~2011-04-16 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 19:04 Rigved Rakshit [this message]
2011-04-17 4:39 ` Distributed Computing Mulyadi Santosa
-- 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=BANLkTin-ucmi-13OdpAViS2RLYKivtgp7Q@mail.gmail.com \
--to=r.phate@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).