From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: remote system call
Date: Thu, 3 Mar 2016 23:37:11 +0700 [thread overview]
Message-ID: <CAGdaadZF-f7h6eEFW=RsVrexorpudYawydPE2ibZLGzWOVzcQg@mail.gmail.com> (raw)
In-Reply-To: <CAKfJ7KJCacyJyNeokCxG5rNCMB-j3bvu83YYe_pUYVofgTombg@mail.gmail.com>
On Thu, Mar 3, 2016 at 6:12 PM, Nitin Varyani <varyani.nitin1@gmail.com>
wrote:
> Hi,
> I want to migrate user context of a process to a remote machine
> (i.e. registers, code, data, virtual memory and program counter) and when
> it makes a system call or file i/o, I want to send that request to its home
> node.
>
> That is, the user process executing at remote node will copy desired
> system call number to %eax of home node and will execute 'int 0x80'. This
> will generate interrupt 0x80 which should be sent to home node and an
> interrupt service routine at home node will be called. This routine will
> execute in ring 0 of home node.
>
> A portion of process context which is system dependent has to be kept at
> the home node.
>
> That is, link to open files and link to kernel stack.
>
> For eg: the following portion of the task_struct has to be kept at home
> node
> /* filesystem information */
> struct fs_struct *fs;
> /* open file information */
> struct files_struct *files;
>
>
>
> Is it feasible? Can someone show some more light into it?
>
> Nitin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
Feasible, yes.
Try to check the source code of MOSIX/OpenMosix or OpenSSI.
Kerrighed is another project which done similar thing too.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/8061dd13/attachment-0001.html
next prev parent reply other threads:[~2016-03-03 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:12 remote system call Nitin Varyani
2016-03-03 16:37 ` Mulyadi Santosa [this message]
2016-03-05 10:28 ` Nitin Varyani
2016-03-05 21:58 ` Valdis.Kletnieks at vt.edu
2016-03-12 17:00 ` Nicholas Mc Guire
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='CAGdaadZF-f7h6eEFW=RsVrexorpudYawydPE2ibZLGzWOVzcQg@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).