[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0905120818290.13234@gandalf.stny.rr.com>
Date: Tue, 12 May 2009 08:20:51 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
cc: Ingo Molnar <mingo@...e.hu>, Chris Friesen <cfriesen@...tel.com>,
Thomas Gleixner <tglx@...utronix.de>,
David Miller <davem@...emloft.net>, linuxppc-dev@...abs.org,
paulus@...ba.org, netdev@...r.kernel.org
Subject: Re: question about softirqs
On Tue, 12 May 2009, Peter Zijlstra wrote:
> On Tue, 2009-05-12 at 11:23 +0200, Ingo Molnar wrote:
> >
> > Yeah, that would be "nice". A single IRQ thread plus the process
> > context(s) doing networking might perform well.
> >
> > Multiple IRQ threads (softirq and hardirq threads mixed) i'm not so
> > sure about - it's extra context-switching cost.
>
> Sure, that was implied by the getting rid of softirqs ;-), on -rt we
> currently suffer this hardirq/softirq thread ping-pong, it sucks.
I'm going to be playing around with bypassing the net-rx/tx with my
network drivers. I'm going to add threaded irqs for my network cards and
have the driver threads do the work to get through the tcp/ip stack.
I'll still keep the softirqs for other cards, but I want to see how fast
it speeds things up if I have the driver thread do it.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists