From: peterz@infradead.org (Peter Zijlstra)
Subject: [ltt-dev] [patch 3/9] LTTng instrumentation tasklets
Date: Wed, 25 Mar 2009 15:17:58 +0100 [thread overview]
Message-ID: <1237990678.7972.1094.camel@twins> (raw)
In-Reply-To: <BD597E014482714090555A6376F9CA8B771BE5A0BD@EXMAIL.ad.emulex.com>
On Wed, 2009-03-25 at 06:52 -0700, Chetan.Loke at Emulex.Com wrote:
> Quick question. I understand this is unrelated to this patch. So I
> apologize in advance.
> Ingo - you mentioned "tasklets are a legacy mechanism". Is there a
> plan to phase them out ? Let me draw a small picture as to what's
> bothering me.
>
> With the SR-IOV support if there are 'N' virtual functions then there
> will be 'N' driver instances(actually N+1, 1 for the PF). If that
> driver drains the responses in the interrupt context then all such
> VF-instances could virtually block everyone else(because SR-IOV guys
> might also have MSI-X enabled).
> So now all such drivers should alter their Rx path.Driver's can queue
> tasklets and can also get the performance they want.
>
> Any suggestions?
Threaded interrupts?
next prev parent reply other threads:[~2009-03-25 14:17 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 15:56 [ltt-dev] [patch 0/9] LTTng core kernel instrumentation Mathieu Desnoyers
2009-03-24 15:56 ` [ltt-dev] [patch 1/9] IRQ handle prepare for instrumentation Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` [ltt-dev] [patch 2/9] LTTng instrumentation - irq Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 17:33 ` Jason Baron
2009-03-24 17:50 ` Ingo Molnar
2009-03-24 17:57 ` Jason Baron
2009-03-24 19:12 ` Ingo Molnar
2009-03-24 20:11 ` Mathieu Desnoyers
2009-03-24 20:51 ` Ingo Molnar
2009-03-25 8:47 ` Ingo Molnar
2009-03-25 18:30 ` Mathieu Desnoyers
2009-03-25 2:00 ` Steven Rostedt
2009-03-26 18:27 ` Mathieu Desnoyers
2009-03-27 22:53 ` Steven Rostedt
2009-04-02 2:42 ` Mathieu Desnoyers
2009-03-25 2:09 ` Steven Rostedt
2009-03-26 18:28 ` Mathieu Desnoyers
2009-03-27 19:18 ` Jason Baron
2009-03-24 19:14 ` Ingo Molnar
2009-03-27 22:12 ` Thomas Gleixner
2009-03-24 15:56 ` [ltt-dev] [patch 3/9] LTTng instrumentation tasklets Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 17:56 ` Ingo Molnar
2009-03-25 13:52 ` Chetan.Loke
2009-03-25 14:17 ` Peter Zijlstra [this message]
2009-03-25 17:37 ` Chetan.Loke
2009-03-25 17:52 ` Steven Rostedt
2009-03-24 15:56 ` [ltt-dev] [patch 4/9] LTTng instrumentation softirq Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 18:01 ` Ingo Molnar
2009-03-24 15:56 ` [ltt-dev] [patch 5/9] LTTng instrumentation scheduler fix task migration Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 17:53 ` Ingo Molnar
2009-03-24 15:56 ` [ltt-dev] [patch 6/9] LTTng instrumentation - timer Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 18:21 ` Ingo Molnar
2009-03-24 19:14 ` Thomas Gleixner
2009-03-24 20:47 ` Ingo Molnar
2009-03-27 22:05 ` Thomas Gleixner
2009-03-24 15:56 ` [ltt-dev] [patch 7/9] LTTng instrumentation - kernel Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 18:33 ` Ingo Molnar
2009-03-25 1:13 ` Rusty Russell
2009-03-25 8:40 ` Ingo Molnar
2009-03-25 13:06 ` Frederic Weisbecker
2009-03-24 15:56 ` [ltt-dev] [patch 8/9] LTTng instrumentation - filemap Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 18:39 ` Ingo Molnar
2009-03-24 15:56 ` [ltt-dev] [patch 9/9] LTTng instrumentation - swap Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 15:56 ` Mathieu Desnoyers
2009-03-24 18:51 ` Ingo Molnar
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=1237990678.7972.1094.camel@twins \
--to=peterz@infradead.org \
/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