public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Scordino <claudio@evidence.eu.com>
To: Soumya K S <ssks.mt@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] DRTL kernel 2.6.32-rc3 : SCHED_EDF, DI RT-Mutex, Deadline Based Interrupt Handlers
Date: Thu, 22 Oct 2009 11:33:34 +0200	[thread overview]
Message-ID: <4AE026EE.9040909@evidence.eu.com> (raw)
In-Reply-To: <e932a33e0910210838j3be9286bo3953c4cae3f0e12e@mail.gmail.com>

Soumya K S ha scritto:
> Hello All,
> 
> We would like to present a patch on Deployment specific Real-Time
> Linux, topic discussed in LinuxCon 2009
> <http://events.linuxfoundation.org/lc09d17>
> 
> The developed framework allows user to specify the real-time
> strategies for a specific real-time scenario. User specifies
> configurations like scheduling policy, Deadline-miss Fault-tolerance
> limit, interrupt priorities, etc. Real-time applications use onetime
> gateway to notify kernel that they require real-time response. All
> applications use existing POSIX APIs. DRTL scheduler is time-aware and
> uses EDF as the scheduling policy.
> 
> The patch consists of Time aware scheduler having SCHED_EDF as the
> scheduling policy, Deadline based scheduling for Interrupt handlers,
> Deadline Inheritance support for RT-Mutexes.
> 
> The patch is for the kernel version 2.6.32-rc3. It has been tested on
> OMAP3530, ATMEL AT91SAM9261 and X86 platforms.
> 
> We look forward for support and feedback about
> DRTL <http://docs.google.com/fileview?id=0BzLQtQ1qAO7uYjYyN2QwNGUtYWE2YS00MDc1LWExYWUtZTliNjNjNmZiZTZj&hl=en>
> and the patch for its feasibility, scalability and performance.
> 
> Many Thanks,
> Soumya KS
> Shubhro Sinha

Hi,

    FYI, a patch to add EDF scheduling to Linux has been already 
proposed in September (see http://lkml.org/lkml/2009/9/22/186), 
discussed on mailing list and presented with a talk at the last 
Real-Time Linux Workshop (RTLWS - 
http://www.osadl.org/Dresden-2009.rtlws11-dresden-2009.0.html).

The patch was initially called "SCHED_EDF". Then, on suggestion of 
Peter, the name has been changed to "SCHED_DEADLINE" and the code moved 
to a public git repository 
(http://gitorious.org/sched_deadline/sched-deadline).

Recently, the patch has been re-submitted to LKML (see 
http://lkml.org/lkml/2009/10/16/161) with many issues fixed. Among them: 
a new behavior of fork(), a new syscall for periodic tasks, flags to 
signal deadline misses and budget overruns. All these changes come from 
the comments and the feedback got on mailing list and at the workshop.

At a first glance, your patch extends sched_param (which may lead to 
compatibility problems with old code), it does not support SMP 
platforms, and it changes the sched_rt code instead of adding a new 
scheduling class.

For the reasons above, I think that we should stick with SCHED_DEADLINE, 
eventually integrating some parts of your code into that project.

Best regards,

              Claudio



  parent reply	other threads:[~2009-10-22  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e932a33e0910210833j1fab6129m23b55101c5978c4a@mail.gmail.com>
2009-10-21 15:38 ` [PATCH] DRTL kernel 2.6.32-rc3 : SCHED_EDF, DI RT-Mutex, Deadline Based Interrupt Handlers Soumya K S
2009-10-22  7:54   ` Raistlin
2009-10-22 14:42     ` Soumya K S
2009-10-25  8:46       ` Raistlin
2009-10-28 14:15         ` Soumya K S
2009-10-28 16:24           ` Raistlin
2009-11-10 14:03             ` Soumya K S
2009-11-10 14:34             ` Peter Zijlstra
2009-10-22  9:33   ` Claudio Scordino [this message]
     [not found]   ` <e932a33e0910220738v3c612d68ve902a770ab0928f4@mail.gmail.com>
2009-10-22 14:40     ` Soumya K S

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=4AE026EE.9040909@evidence.eu.com \
    --to=claudio@evidence.eu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ssks.mt@gmail.com \
    --cc=tglx@linutronix.de \
    /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