From: Daniel Walker <dwalker@mvista.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Thread Migration Preemption
Date: Fri, 06 Jul 2007 08:43:39 -0700 [thread overview]
Message-ID: <1183736619.19602.7.camel@imap.mvista.com> (raw)
In-Reply-To: <1183732495.17319.133.camel@localhost.localdomain>
On Fri, 2007-07-06 at 10:34 -0400, Steven Rostedt wrote:
> thing is that in RT an IRQ thread might service a softirq if that
> softirq thread is of the same priority as the IRQ thread. The difference
> between an IRQ thread and a softirq thread is that the IRQ thread may
> migrate but the softirq thread may not. So to do this performance
> enhancement, we need to temporarily pin the IRQ thread to the CPU, which
> is expensive (set_cpus_allowed). This would make it much simpler and
> light weight to implement.
Are there any other reasons?
Daniel
next prev parent reply other threads:[~2007-07-06 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 21:51 Mathieu Desnoyers
2007-07-05 22:46 ` Steven Rostedt
2007-07-06 6:12 ` Nick Piggin
2007-07-06 14:34 ` Mathieu Desnoyers
2007-07-06 14:34 ` Steven Rostedt
2007-07-06 15:43 ` Daniel Walker [this message]
2007-07-08 9:05 ` Nick Piggin
2007-07-10 23:39 ` Matt Mackall
2007-07-11 0:02 ` Nick Piggin
2007-07-11 0:36 ` Matt Mackall
2007-07-11 0:55 ` Mathieu Desnoyers
2007-07-11 1:15 ` Nick Piggin
2007-07-06 11:59 ` Andi Kleen
2007-07-06 14:41 ` Mathieu Desnoyers
2007-07-06 17:11 ` Andi Kleen
2007-07-11 4:57 ` Mathieu Desnoyers
2007-07-23 18:33 ` Ingo Molnar
2007-07-06 6:02 Oleg Nesterov
2007-07-06 14:23 ` Mathieu Desnoyers
2007-07-06 14:56 ` Oleg Nesterov
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=1183736619.19602.7.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@redhat.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®