public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <finarfin@dreamos.org>
To: linux-kernel@vger.kernel.org
Subject: SCHED_EDF infos
Date: Wed, 29 Apr 2009 23:36:13 +0200	[thread overview]
Message-ID: <164c92d827cbee86ba2c5621716309e6@localhost> (raw)

Hi,
I'm new to this list,

Actually i'm near to BS degree in computer science, and for thesis my
Operating System Professor suggested to complete (or begin?) SCHED_EDF for
linux. 

Now i don't know if i'm able to do that, i'm new to linux-kernel
development:
1. Someone is already working on that? This task is still available?
2. Now there was something implemented about sched_edf?
3. Into sched-rt-groups.txt there was something that was not very clear (in
my opinion): 
   The next project will be SCHED_EDF (Earliest Deadline First scheduling)
to bring
   full deadline scheduling to the linux kernel. Deadline scheduling the
above
   groups and treating end of the period as a deadline will ensure that
they both
   get their allocated time.

   Implementing SCHED_EDF might take a while to complete. Priority
Inheritance is
   the biggest challenge as the current linux PI infrastructure is geared
towards
   the limited static priority levels 0-139. With deadline scheduling you
need to
   do deadline inheritance (since priority is inversely proportional to the
   deadline delta (deadline - now).
   
   Priority inheritance is a different task? 
4. In your opinion three months will be sufficient for that task? (yeah
probably this seems a silly question, but if working on that take me a too
long time i think i have to find another thesis :D i wish to have my degree
before the end of this year)  
5. For implement that algorithm the general EDF documentation will be
sufficient? There are some special requisites?
6. if you have any suggestion i'll be glad to receive it :)

I hope that this mail doesn't sound useless. 

Thank you, 
Ivan



             reply	other threads:[~2009-04-29 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 21:36 finarfin [this message]
2009-04-30  7:39 ` SCHED_EDF infos Henrik Austad
2009-05-08  2:35   ` GeunSik Lim
2009-05-08  9:10     ` Henrik Austad
2009-05-30 11:38       ` GeunSik Lim
2009-05-30 13:34         ` Henrik Austad
2009-05-30 14:46           ` GeunSik Lim
2009-05-30 15:04             ` Henrik Austad
2009-05-30 19:15       ` Peter Zijlstra
2009-05-30 20:40         ` Henrik Austad
2009-05-30 21:15           ` Peter Zijlstra

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=164c92d827cbee86ba2c5621716309e6@localhost \
    --to=finarfin@dreamos.org \
    --cc=linux-kernel@vger.kernel.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