Hello!
Quoting r. Sean Hefty ([EMAIL PROTECTED]) Re: [openib-general] Re: OpenIB
Thread Usage:
Roland Dreier wrote:
Sean I thought about this approach, but wasn't sure about taking
Sean a context switch. I guess with QP redirection, this
Sean wouldn't be an issue though.
I
Sean I tried to keep the MAD layer from knowing about completion
Sean threads to make it easier to change it later. I think once
Sean we get to some CM performance testing, we can try adjusting
Sean the threading model to gives us the best performance and
Sean scalability: one
Roland Dreier wrote:
I think the CM ends up needing its own set of workqueues so that it
can queue MAD processing along with time wait events etc. Also we
don't want the CM to block general MAD processing while it waits for
things like QP modify.
I thought about this approach, but wasn't sure
On Fri, 2004-11-19 at 12:36, Sean Hefty wrote:
idle threads have pretty minimal impact beyond the memory they use.
However on say a 512 CPU box with 6 HCAs, we would create 6000+ kernel
threads, which seems pretty excessive.
Wouldn't it still just be one per port, or 12 total?
It's
Sean I thought about this approach, but wasn't sure about taking
Sean a context switch. I guess with QP redirection, this
Sean wouldn't be an issue though.
I don't think there's a choice. If the CM processes MADs from one queue
and time wait expirations from another, it's not
