From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [RFC Patch 0/3] Putting the "Simple" back in sedf. Date: Fri, 14 Mar 2014 19:22:30 +0000 Message-ID: <532356F6.4030209@eu.citrix.com> References: <1394824400-2796-1-git-send-email-nate.studer@dornerworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1394824400-2796-1-git-send-email-nate.studer@dornerworks.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Nathan Studer , xen-devel@lists.xen.org Cc: Ian Campbell , Xi Sisu , Stefano Stabellini , Ian Jackson , Robert VanVossen , Dario Faggioli List-Id: xen-devel@lists.xenproject.org On 03/14/2014 07:13 PM, Nathan Studer wrote: > From: Nathan Studer > > With the increased interest in embedded Xen, there is a need for a suitable > real-time scheduler. The arinc653 scheduler currently only supports a > single core and has limited niche appeal, while the sedf scheduler is > widely consider deprecated and is currently a mess. > > Since both the CBS scheduler proposed by Dario and the schedulers of Xen-RT > use an edf scheduler as the lowest-level scheduling mechanism, it seems > worthwhile to start repurposing the sedf scheduler instead of creating a > completely new scheduler. > > This patchset begins this repurposing by removing the extra scheduling code > that has built up over the years, and returns the sedf scheduler to its > simple roots. Hey Nate, Thanks for these patches -- what you describe at a high level, making sedf a suitable rts for embedded applications, sounds like a great idea. I think what might be helpful in evaluating whether these patches are a good idea at the high level is a bit of a description of where you see this going long-term. Can you sketch out, at a high level, what you envision the sedf scheduler becoming? What kinds of parameters and features *will* it have? -George