[okl4-developer] What's Wombat priority?

[Abi Nourai]

Hi Antonin,

I've noticed you're digging deeper into the belly of the beast that is  
OKL4 every day.  Keep it up !

I'll answer the easy questions for you immediately, and leave the more  
tricky ones for tomorrow.

255 is highest priority.  0 is the lowest priority.

Wombat actually consists of two threads, a thread that receives device  
interrupts (including timer ticks), and another thread that  
effectively does 99% of the work (sometimes called the worker thread  
or the syscall thread).

FYI one reason for the existence of threads is so that the syscall  
thread (think of it as *the* linux kernel thread) can simulate  
disabling interrupts by telling the interrupt thread 'hey, when you  
get an interrupt, I don't want to know about it - so keep track of it  
internally, and deliver it to me by exreg only when I 'enable'  
interrupts' .

In this model, the interrupt thread effectively servers fulfills the  
function of the hardware in a non-virtualized environment.  It takes  
the interrupt trap, and delivers it to the OS (syscall thread) when  
interrupts are enabled.  Hence the interrupt thread runs at a higher  
priority (100) than the syscall thread (99).

Regards
Abi

On 02/04/2008, at 1:34 AM, Antonin SUBTIL wrote:
> Hello,
>
>
> I had a look to Sconscript in Iguana, and here is my question :
> "weaver = env.WeaverIguanaProgramServer(server_name =  
> "OKL4_HELLO_SERVER", priority=50)"
> Are priorities on 0-255 ? Is 255 big or low priority?
> What's Wombat priority? (If I'm trying to put some real-time server,  
> I should know it... yet I was able too find it)
>
> Do anyone have a doc of this function? There's other arguments for  
> Linux I would like to understand...
>
>
> Thanks
>
>
> -- 
> Antonin Subtil,
> 35 rue Donissan
> FR-33000 Bordeaux
> +33 (0)6.77.40.17.69
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer