From: Arjan van de Ven <arjan@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, mingo@elte.hu, rostedt@goodmis.org,
jonathan@jonmasters.org
Subject: Re: [patch 4/4] genirq: add support for threaded interrupt handlers
Date: Fri, 27 Feb 2009 07:06:33 -0800 [thread overview]
Message-ID: <20090227070633.2c3fc04e@infradead.org> (raw)
In-Reply-To: <1235721910.4948.1321.camel@laptop>
On Fri, 27 Feb 2009 09:05:10 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
>
> Right, Thomas did the EHCI usb driver, the network driver you propose
> is a tad hard since it relies on the whole network stack softirq
> stuff. Re-working the whole net-stack to make use of threaded
> handlers is a massive undertaking -- although I seem to remember
> someone doing it a few years back and seeing a general performance
> improvement, Thomas still got a link to that work?
we shouldn't have to; just running the softirq handler from the irq
thread should work, and not lose real performance.
Sure you're not going to get a performance gain that you could get
but it still works.
or am I missing something?
(and esp for things like wireless drivers, that should be just fine; I
can understand hesitation to do 10g ethernet drivers right away ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-02-27 15:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 13:28 [patch 0/4] genirq: add infrastructure for threaded interrupt handlers V2 Thomas Gleixner
2009-02-26 13:28 ` [patch 1/4] genirq: make irqreturn_t an enum Thomas Gleixner
2009-03-25 19:51 ` Geert Uytterhoeven
2009-02-26 13:28 ` [patch 2/4] genirq: use kzalloc instead of explicit zero initialization Thomas Gleixner
2009-02-26 13:28 ` [patch 3/4] genirq: add a quick check handler Thomas Gleixner
2009-02-26 23:03 ` Andrew Morton
2009-02-26 23:11 ` Thomas Gleixner
2009-02-28 22:24 ` Christoph Hellwig
2009-03-01 9:44 ` Thomas Gleixner
2009-03-05 19:59 ` Sven-Thorsten Dietrich
2009-03-17 7:54 ` Christoph Hellwig
2009-03-17 15:29 ` Steven Rostedt
2009-02-26 13:28 ` [patch 4/4] genirq: add support for threaded interrupt handlers Thomas Gleixner
2009-02-26 23:32 ` Andrew Morton
2009-02-27 5:27 ` Arjan van de Ven
2009-02-27 5:45 ` Andrew Morton
2009-02-27 7:18 ` Peter Zijlstra
2009-02-27 7:48 ` Andrew Morton
2009-02-27 8:05 ` Peter Zijlstra
2009-02-27 8:15 ` Andrew Morton
2009-02-27 15:06 ` Arjan van de Ven [this message]
2009-02-27 15:30 ` Steven Rostedt
2009-02-28 13:46 ` Stefan Richter
2009-03-02 13:21 ` Peter Zijlstra
2009-02-28 17:13 ` Andi Kleen
2009-02-27 16:43 ` Thomas Gleixner
2009-02-26 15:26 ` [patch 0/4] genirq: add infrastructure for threaded interrupt handlers V2 Jon Masters
2009-03-05 20:03 ` Sven-Thorsten Dietrich
2009-02-28 22:10 ` Christoph Hellwig
2009-03-01 9:43 ` Thomas Gleixner
2009-03-05 8:40 ` [ANNOUNCE] USB genirq " Sven-Thorsten Dietrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090227070633.2c3fc04e@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox