From: jeshkumar555@gmail.com (jeshkumar555@gmail.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Re: Creating scheduler
Date: Thu, 07 Feb 2013 10:15:00 +0530 [thread overview]
Message-ID: <5113314a.4955420a.3012.22e9@mx.google.com> (raw)
Hey Peter,
Think First link is useful for scheduler, thanks :).
Sent from my HTC
Excuse for typo.
----- Reply message -----
From: "Peter Teoh" <htmldeveloper@gmail.com>
Date: Thu, Feb 7, 2013 9:38 am
Subject: Creating scheduler
To: "jeshkumar555 at gmail.com" <jeshkumar555@gmail.com>
Cc: "kernelnewbies" <Kernelnewbies@kernelnewbies.org>
well...u asked for it:
http://abstract.cs.washington.edu/~shwetak/classes/ee472/assignments/lab2/lab2.pdf
http://www.cs.cmu.edu/~410-s07/p3/kernel.pdf
http://web.stonehill.edu/compsci/CS314/Assignments/Assignment0.pdf
http://www.cs.amherst.edu/~sfkaplan/courses/2012/spring/cs261/assignments/project-1.pdf
etc...googling returned me 27000 links....
On Thu, Feb 7, 2013 at 1:49 AM, jeshkumar555 at gmail.com <
jeshkumar555@gmail.com> wrote:
> Hi all :),
>
> Can anyone suggest a good tutorial to create our own scheduler ?
>
>
> Sent from my HTC
> Excuse for typo.
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
--
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130207/49f4281e/attachment.html
next reply other threads:[~2013-02-07 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 4:45 jeshkumar555 [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-06 17:49 Creating scheduler jeshkumar555
2013-02-06 18:16 ` Valdis.Kletnieks at vt.edu
2013-02-06 19:40 ` Jonathan Neuschäfer
2013-02-06 20:35 ` Valdis.Kletnieks at vt.edu
2013-02-07 4:08 ` Peter Teoh
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=5113314a.4955420a.3012.22e9@mx.google.com \
--to=jeshkumar555@gmail.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).