Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Understading priority and threading model in io-pkt: (5 Items)
   
Understading priority and threading model in io-pkt  
After specifying elevated interface-specific priorities at the driver command-line options when the driver is done 
servicing the hardware at this elevated priority (on a receive event), and the thread becomes the TCP stack thread, does
 the TCP stack operation continue at the same priority as the driver?
Re: Understading priority and threading model in io-pkt  
On Wed, Aug 25, 2010 at 09:10:38AM -0400, Gervais Mulongoy wrote:
> After specifying elevated interface-specific priorities at the driver command-line options when the driver is done 
servicing the hardware at this elevated priority (on a receive event), and the thread becomes the TCP stack thread, does
 the TCP stack operation continue at the same priority as the driver?

For native drivers yes, if there's still work to do, otherwise it
blocks in MsgReceive().

Regards,

-seanb
Re: Understading priority and threading model in io-pkt  
An additional question,

Are there any stack operations or networking events that can bypass invocation of a filter or once a filter is in place 
it always gets a chance to intercept data?
Re: Understading priority and threading model in io-pkt  
On Wed, Aug 25, 2010 at 09:35:23AM -0400, Gervais Mulongoy wrote:
> An additional question,
> 
> Are there any stack operations or networking events that can bypass invocation of a filter or once a filter is in 
place it always gets a chance to intercept data?
> 

We're talking about pfil hooks?  It depends on where you
hook up.  If you're at the ip layer for example and it's
not a ip packet or it is an ip packet but it gets
fast-forwarded out you won't see it.

-seanb
Re: Understading priority and threading model in io-pkt  
Is there a way to control the priority of the stack threads? Is the default prio 21?