Re: Call for performance evaluation: net.isr.direct

2005-10-24 Thread Mike Tancsa
At 12:12 PM 05/10/2005, Robert Watson wrote: Obviously, this is about two things: performance, and stability. Many of us ... Of particular interest is if changing to direct dispatch hurts performance in your environment, and understanding why that is. I enabled this last Monday on 2 SMP

Re: Call for performance evaluation: net.isr.direct

2005-10-12 Thread Robert Watson
On Wed, 12 Oct 2005 [EMAIL PROTECTED] wrote: At Tue, 11 Oct 2005 15:01:11 +0100 (BST), rwatson wrote: If I don't hear anything back in the near future, I will commit a change to 7.x to make direct dispatch the default, in order to let a broader community do the testing. :-) If you are setup t

Re: Call for performance evaluation: net.isr.direct

2005-10-12 Thread gnn
At Tue, 11 Oct 2005 15:01:11 +0100 (BST), rwatson wrote: > If I don't hear anything back in the near future, I will commit a > change to 7.x to make direct dispatch the default, in order to let a > broader community do the testing. :-) If you are setup to easily > test stability and performance re

Re: Call for performance evaluation: net.isr.direct

2005-10-11 Thread Robert Watson
On Wed, 5 Oct 2005, Robert Watson wrote: In 2003, Jonathan Lemon added initial support for direct dispatch of netisr handlers from the calling thread, as part of his DARPA/NAI Labs contract in the DARPA CHATS research program. Over the last two years since then, Sam Leffler and I have worked

Call for performance evaluation: net.isr.direct

2005-10-05 Thread Robert Watson
In 2003, Jonathan Lemon added initial support for direct dispatch of netisr handlers from the calling thread, as part of his DARPA/NAI Labs contract in the DARPA CHATS research program. Over the last two years since then, Sam Leffler and I have worked to refine this implementation, removing