From: henrik@austad.us (Henrik Austad)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Process Scheduling Algorithm
Date: Mon, 15 Feb 2016 17:52:31 +0100 [thread overview]
Message-ID: <20160215165231.GD21526@icarus.home.austad.us> (raw)
In-Reply-To: <CAKfJ7KLaNMabXoVdBTHC2hATkbgesmSi4uTPwGdCdKqMzJCPKg@mail.gmail.com>
On Mon, Feb 15, 2016 at 09:35:28PM +0530, Nitin Varyani wrote:
> Hi,
Hi Nitin,
> I am given a task to design a distributed process scheduling algorithm.
> Current distributed OS are patch work over the linux kernels, that is, they
> are responsible for load balancing through process migration but the
> scheduling is taken care by the single machine linux kernels.
Hmm, are you talking about HPC clusters or other large machines here? I'm
not familiar with this, so a few references to existing designs would be
appreciated.
> My task is to make the scheduling algorithm itself as distributed.
Apart from my comment below, it sounds like a really interesting project.
Is this a research-project or something commercial?
> That is a scheduler itself makes a decision whether to migrate a task or
> to keep the task in the current system. I need some design aspects of
> how to achieve it. Another thing which I want to know is that whether
> this job is possible for a kernel newbie like me. Need urgent help. Nitin
Uhm, ok. I think this is _way_ outside the scope of Kernelnewbies, and it
is definitely not a newbie project.
If you are really serious about this, I'd start with listing all the
different elements you need to share and then an initial idea as to how to
share those between individual systems. I have an inkling that you'll find
out quite fast as to why the current kernel does not support this out of
the box.
--
Henrik Austad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/8a8b01b8/attachment.bin
next prev parent reply other threads:[~2016-02-15 16:52 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 [this message]
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
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=20160215165231.GD21526@icarus.home.austad.us \
--to=henrik@austad.us \
--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).