From: dingel@linux.vnet.ibm.com (Dominik Dingel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Process Scheduling Algorithm
Date: Tue, 16 Feb 2016 12:22:17 +0100 [thread overview]
Message-ID: <20160216122217.21c6096e@BR9TG4T3.de.ibm.com> (raw)
In-Reply-To: <CAKfJ7KK_eYn7OD4VknHSYmeiK2vR+90RN79BW2QMc1y3ZM3T5Q@mail.gmail.com>
On Tue, 16 Feb 2016 16:13:25 +0530
Nitin Varyani <varyani.nitin1@gmail.com> wrote:
It is common practice to shorten your answers to mailinglists.
> The essence of the discussion is that :
>
> We can run each process in a container and migrate the container itself.
> Migration can be done based on work stealing. As far as communication
> between processes in different containers is concerned, can't we use
> sockets?
>
Migration can be done based on work stealing sounds misleading. Maybe something like:
Nodes might apply the work stealing pattern by migrating the workload, encapsulated in the container.
That would be the idea, if that actually works and how it would perform is up to that experiment ;).
That is for new applications possible, but there may be "legacy" applications which rely on communication methods like shared memory, and pipes.
If this ends in an research paper I would like to read it.
Dominik
next prev parent reply other threads:[~2016-02-16 11:22 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 [this message]
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
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=20160216122217.21c6096e@BR9TG4T3.de.ibm.com \
--to=dingel@linux.vnet.ibm.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).