Real Time threads
"Salvatore Benedetto" <[email protected]> Tue, 6 May 2008 11:51:15 +0000
| Newsgroups | gmane.os.openbeos.kernel.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi there, quick questions: how is Haiku supposed to behave with Real Time threads? Do we have to do our best, or we have to guarantee what they ask if we accept to scheduler them? Or return a message, not a error, if we can't guarantee what they ask in order to prevent starvation for other threads. For example, let's say we have a thread of a 3D shooting game that ask to be schedule periodically in order to render images, and another thread that ask be run periodically to reproduce the sounds of the game. And all this are real time threads, or _happen_to_be_ real time threads( say we return 120 with suggest_thread_priority). How should we cope with that? I guess our primary concern is to avoid starvation of the other threads anyway right? But on the other hand, if we accept a thread, we have to guarantee what they ask. Should we provide some functions about periodic task like this? If so, we should adopt some kind of hard real time scheduler for this kind of thread in order to guarantee what they ask, but also we have to make sure we don't create starvation for other backgrounds, low priority threads. Regards, -- Salvatore Benedetto (a.k.a. emitrax) Student of Computer Engineer University of Pisa www.haiku-os.it ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone