On Wed, 17 Feb 2016 10:21:35 +0530, Nitin Varyani said: > Actually it is a master's thesis research project as of now. I am ready to > boil down to the most basic implementation of distributed linux kernel. > Assume there is no network connection and no open files. We can drop even > more assumptions if it becomes complicated. Once this basic implementation > is successful, we can go ahead with a more complicated version. The next > task is to integrate the migration code in the linux kernel. What is the > most easy way of implementing it. If you get it to where you can migrate a process on command controlled by a userspace process, the scheduler part will be trivial. And note that the choice of which process to migrate where is sufficiently "policy" that it belongs in userspace - see how cgroups and containers are kernel mechanisms that are controlled by userspace. You want to follow that model if you intend for this to be upstreamed rather than just another dead master's thesis.
Attachment:
pgp1tUBys5D2e.pgp
Description: PGP signature
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
