Messages in this thread | | | From | Rafael Fernandez <> | Date | Fri, 1 Apr 2011 09:19:28 -0500 | Subject | Re: Minimum time slice for relaible Linux execution |
| |
Hi,
This is pretty interesting to me. How would your framework handle an RT application that does quite a bit of I/O? Does it block and go to Linux, get serviced, and come back?
Thank you, Rafael
On Thu, Mar 31, 2011 at 7:13 AM, limp <johnkyr83@hotmail.com> wrote: > Dear all, > > I have developed a framework similar to a hypervisor that switches between > Linux and a RT domain. > As RT priority is of highest importance, I want to give more time to the RT > domain *but* I also want to give Linux adequate time for being able to > operate. > > Could anyone advise me on how to determine the minimum possible time slice > that I can give to Linux so that it doesn't crash? > > That is, if I periodically execute my RT domain every ms and then I switch > to Linux, what's the minimum time that should be given to Linux, until the > next RT domain execution? > > NOTE: The RT domain and Linux are not executed concurrently, i.e. the RT > domain is executed first and then Linux executes until the next RT domain > execution. > > Thank you all in advance. > > John K. > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |