Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - timeslice: (4 Items)
   
timeslice  
in io-pkt 1 system scope thread mapped to a couple of process scope threads, so it must only have 1 timeslice for all 
these process scope threads, right?
Re: timeslice  
On Mon, Oct 27, 2008 at 09:29:06AM -0400, Yao Zhao wrote:
> in io-pkt 1 system scope thread mapped to a couple of process scope threads, so it must only have 1 timeslice for all 
these process scope threads, right?

I'm not sure what you mean exactly.  The normal
scheduling rules apply.

-seanb
Re: timeslice  
Let's say there are 2 process in one system:
process1: thread1 thread2
io-pkt    : thread1 thread2

if they all have same priority 21, then in theory process1 should own 2/3 cpu and io-pkt owns 1/3 cpus, thread1 of io-
pkt didn't do anything.

process 1 attached to 2 interrupts and io-pkt attached to 2 interrupts too,  and all of interrupts are active. Because 
thread2 is system scope thread so it can only use 1/3 cpu although in thread2 there are more process scope threads, if 
we say there are 3 system scope threads in io-pkt and 2 of them are responsible for the 2 interrupts then we have 1/2 
cpu. 
let's say it is only layer2 forwarding, no layer3 involved so stack should not be the bottleneck.
Re: timeslice  
On Wed, Oct 29, 2008 at 10:34:01AM -0400, Yao Zhao wrote:
> Let's say there are 2 process in one system:
> process1: thread1 thread2
> io-pkt    : thread1 thread2
> 
> if they all have same priority 21, then in theory process1 should own 2/3 cpu and io-pkt owns 1/3 cpus, thread1 of io-
pkt didn't do anything.
> 
> process 1 attached to 2 interrupts and io-pkt attached to 2 interrupts too,  and all of interrupts are active. Because
 thread2 is system scope thread so it can only use 1/3 cpu although in thread2 there are more process scope threads, if 
we say there are 3 system scope threads in io-pkt and 2 of them are responsible for the 2 interrupts then we have 1/2 
cpu. 
> let's say it is only layer2 forwarding, no layer3 involved so stack should not be the bottleneck.

I'm more confused than before.  What's the question?
What's a "system scope thread"?  If there are 2 threads
in io-pkt how can it have "3 system scope threads"?

-seanb