<div dir="ltr">Codes are huge and documentation is negligible. How can I separate whay I want to achieve from that big code?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 3, 2016 at 10:07 PM, Mulyadi Santosa <span dir="ltr"><<a href="mailto:mulyadi.santosa@gmail.com" target="_blank">mulyadi.santosa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Mar 3, 2016 at 6:12 PM, Nitin Varyani <span dir="ltr"><<a href="mailto:varyani.nitin1@gmail.com" target="_blank">varyani.nitin1@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Hi,</div><div> 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. </div><div><br></div><div>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.</div><div><br></div><div>A portion of process context which is system dependent has to be kept at the home node.</div><div><br></div><div>That is, link to open files and link to kernel stack. </div><div><br></div><div>For eg: the following portion of the task_struct has to be kept at home node</div><div>/* filesystem information */</div><div> struct fs_struct *fs;</div><div>/* open file information */</div><div> struct files_struct *files;</div><div><br></div><div><br></div><div><br></div><div>Is it feasible? Can someone show some more light into it?</div><span><font color="#888888"><div><br></div><div>Nitin</div></font></span></div>
<br></div></div>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">Feasible, yes.<br><br></div><div class="gmail_extra">Try to check the source code of MOSIX/OpenMosix or OpenSSI.<br><br></div><div class="gmail_extra">Kerrighed is another project which done similar thing too.<span class="HOEnZb"><font color="#888888"><br><br clear="all"></font></span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br>-- <br><div>regards,<br><br>Mulyadi Santosa<br>Freelance Linux trainer and consultant<br><br>blog: <a href="http://the-hydra.blogspot.com" target="_blank">the-hydra.blogspot.com</a><br>training: <a href="http://mulyaditraining.blogspot.com" target="_blank">mulyaditraining.blogspot.com</a></div>
</div></font></span></div>
</blockquote></div><br></div>