From: nayobix@nayobix.org (Boyan Vladinov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Process scheduling
Date: Wed, 17 Feb 2016 23:11:38 +0200 [thread overview]
Message-ID: <56C4E20A.4090601@nayobix.org> (raw)
In-Reply-To: <20160217162341.GB21722@kroah.com>
Check here:
https://www.kernel.org/doc/Documentation/scheduler/sched-design-CFS.txt
and
http://www.ibm.com/developerworks/library/l-completely-fair-scheduler/
Regards,
Boyan Vladinov
On 17.02.2016 18:23, Greg KH wrote:
> On Wed, Feb 17, 2016 at 12:48:33PM +0530, Nitin Varyani wrote:
>> It is similar to openMosix but still quite different. Open Mosix is built on
>> the top of existing linux kernels. The scheduling is taken care by the existing
>> linux kernels. Open Mosix is responsible for workload distribution. This
>> project is first of its kind.
> No, it's not, it's been tried before, I suggest doing a bit more
> research before making statements like that.
>
> good luck,
>
> greg k-h
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2016-02-17 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 6:12 Process scheduling Nitin Varyani
2016-02-13 8:49 ` Henrik Austad
2016-02-13 9:42 ` Nitin Varyani
[not found] ` <CAKfJ7KLrDSLuw-8CQg4jvKdnPRvQqAXHE4Wf+sSZYqJYdzn3dg@mail.gmail.com>
2016-02-15 12:37 ` Nitin Varyani
2016-02-17 6:10 ` Mulyadi Santosa
2016-02-17 7:18 ` Nitin Varyani
2016-02-17 16:23 ` Greg KH
2016-02-17 21:11 ` Boyan Vladinov [this message]
2016-02-17 21:13 ` Boyan Vladinov
-- strict thread matches above, loose matches on Subject: below --
2016-02-08 8:50 Process Scheduling Nitin Varyani
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=56C4E20A.4090601@nayobix.org \
--to=nayobix@nayobix.org \
--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.