All of lore.kernel.org
 help / color / mirror / Atom feed
From: mfidelman@meetinghouse.net (Miles Fidelman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Process Scheduling Algorithm
Date: Wed, 17 Feb 2016 01:37:06 -0500	[thread overview]
Message-ID: <56C41512.4000100@meetinghouse.net> (raw)
In-Reply-To: <21502.1455689456@turing-police.cc.vt.edu>



On 2/17/16 1:10 AM, Valdis.Kletnieks at vt.edu wrote:
> 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.
>

If you want some ideas about distributed process scheduling, you might 
want to explore how Erlang's run-time works - it's all about massive 
concurrency and scheduling processes (well, really light-weight 
processes) across multiple cores.  If you google "distributed process 
scheduling erlang" you'll also find some work about process scheduling 
across clusters, particularly for gaming environments.

How much might be applicable in a linux kernel environment is unclear - 
but, then, it's your research project.

Miles Fidelman


In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra

  reply	other threads:[~2016-02-17  6:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 16:05 Distributed Process Scheduling Algorithm Nitin Varyani
2016-02-15 16:52 ` Henrik Austad
2016-02-16  4:48   ` Nitin Varyani
2016-02-16  5:13     ` Valdis.Kletnieks at vt.edu
2016-02-16  8:42       ` Dominik Dingel
2016-02-16  9:46         ` Nitin Varyani
2016-02-16 10:43           ` Nitin Varyani
2016-02-16 11:22             ` Dominik Dingel
2016-02-16 16:35         ` Valdis.Kletnieks at vt.edu
2016-02-17  4:51           ` Nitin Varyani
2016-02-17  6:10             ` Valdis.Kletnieks at vt.edu
2016-02-17  6:37               ` Miles Fidelman [this message]
2016-02-17 10:35               ` Nitin Varyani
2016-02-17 15:32                 ` Greg KH
2016-02-18  4:35                   ` Nitin Varyani
2016-02-18  9:31                     ` Mulyadi Santosa
2016-02-19  5:06                     ` Greg KH
2016-02-19 15:31                       ` Ruben Safir

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=56C41512.4000100@meetinghouse.net \
    --to=mfidelman@meetinghouse.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.