From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] RT: Preemptible Function-Call-IPI Support
Date: Tue, 31 Jul 2007 11:25:21 +0200 [thread overview]
Message-ID: <20070731092521.GA16177@elte.hu> (raw)
In-Reply-To: <20070731092119.GA15968@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> * Gregory Haskins <ghaskins@novell.com> wrote:
>
> > This code allows FUNCTION_CALL IPIs to become preemptible by
> > executing them in kthread context instead of interrupt context.
> > They are referred to as "Virtual Function Call IPIs" (VFCIPI)
> > because we no longer rely on the actual FCIPI facility. Instead we
> > schedule a thread to run. This essentially replaces the synchronous
> > FCIPI with an async RESCHEDULE IPI.
>
> why do we need this? It's quite complex and brings little extra
> AFAICS. See the "schedule_on_each_cpu-enhance.patch" from Peter
> Ziljstra that lets a function to be executed on all CPUs. That should
> be extended (trivially) to execute a function on another CPU. That's
> all we need.
as far as the prioritization of function calls goes, _that_ makes sense,
but it should not be a separate API but should be done to our normal
workqueue APIs. That not only extends the effects of priorities to all
current workqueue using kernel subsystems, but also keeps the API more
unified. We really dont want to have too many -rt specific APIs.
Ingo
next prev parent reply other threads:[~2007-07-31 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070730211350.5162.99143.stgit@novell1.haskins.net>
[not found] ` <20070730211539.5162.87483.stgit@novell1.haskins.net>
[not found] ` <20070731091903.GA15822@elte.hu>
2007-07-31 9:21 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Ingo Molnar
2007-07-31 9:25 ` Ingo Molnar [this message]
2007-07-31 14:26 ` Gregory Haskins
2007-07-31 14:26 ` Gregory Haskins
2007-07-31 20:14 ` Gregory Haskins
2007-07-31 11:44 Gregory Haskins
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 12:11 Gregory Haskins
2007-07-31 14:22 ` Ingo Molnar
2007-07-31 13:24 [PATCH 0/2][RFC] VFCIPI v3 Gregory Haskins
2007-07-31 13:24 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
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=20070731092521.GA16177@elte.hu \
--to=mingo@elte.hu \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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