kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Distributed Process Scheduling Algorithm
Date: Thu, 18 Feb 2016 21:06:05 -0800	[thread overview]
Message-ID: <20160219050605.GA11210@kroah.com> (raw)
In-Reply-To: <CAKfJ7KJNiiV=xgdjDLm68nVORhg_CMdqeTVaEGor1K3X0jk69A@mail.gmail.com>

On Thu, Feb 18, 2016 at 10:05:40AM +0530, Nitin Varyani wrote:
> @ Greg: Since I am very new to the field, with the huge task in hand
> and a short time span of 3 months given for this project,

3 months?  That's way too short, this is a multi-year/decade type
research project.  You can barely write a "simple" kernel driver in 3
months start to finish unless you _really_ know what you are doing.

I suggest get a new professor / advisor, this one doesn't seem to
realize the scope of the work involved :)

good luck!

greg k-h

  parent reply	other threads:[~2016-02-19  5:06 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
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 [this message]
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=20160219050605.GA11210@kroah.com \
    --to=greg@kroah.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).