From: Thomas Gleixner <tglx@linutronix.de>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH -tip] sched/rt: Fix locality of threaded interrupt handlers
Date: Mon, 14 Jan 2013 12:19:52 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1301141217300.7475@ionos> (raw)
In-Reply-To: <6b08a3c5c16284fd0221c2b564d451b4b9dcbf18.1357896654.git.agordeev@redhat.com>
On Fri, 11 Jan 2013, Alexander Gordeev wrote:
> When a interrupt affinity mask targets multiple CPUs, the
> RT scheduler selects a runqueue for RT task corresponding
> to a threaded interrupt handler without consideration of
> where the interrupt is actually gets delivered. It leads
> to a suboptimal condition when a hardware interrupt handler
> executes on one CPU while the threaded interrupt handler
> executes on another CPU.
>
> This fix alters the behaviour of threaded handler wake-ups
> by getting priority to a CPU where the hardware interrupt
> handler is executing. As result, most of the time both
> halves of interrupt handling are kept local.
Nice one.
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> ---
> include/linux/sched.h | 2 ++
> kernel/irq/handle.c | 2 +-
> kernel/sched/core.c | 5 +++++
> kernel/sched/rt.c | 27 +++++++++++++++++++--------
> 4 files changed, 27 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 206bb08..cd9cb42 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1061,6 +1061,7 @@ struct sched_domain;
> #define WF_SYNC 0x01 /* waker goes to sleep after wakup */
> #define WF_FORK 0x02 /* child wakeup after fork */
> #define WF_MIGRATED 0x04 /* internal use, task got migrated */
> +#define WF_INTR 0x08 /* threaded handler wakeup from intr */
Please make this WF_LOCAL or something like that. There is no point to
tie this functionality to interrupt threads. The scheduler does not
care at all.
> #define ENQUEUE_WAKEUP 1
> #define ENQUEUE_HEAD 2
> @@ -2207,6 +2208,7 @@ extern void xtime_update(unsigned long ticks);
>
> extern int wake_up_state(struct task_struct *tsk, unsigned int state);
> extern int wake_up_process(struct task_struct *tsk);
> +extern int wake_up_handler(struct task_struct *tsk);
> extern void wake_up_new_task(struct task_struct *tsk);
> #ifdef CONFIG_SMP
> extern void kick_process(struct task_struct *tsk);
> diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
> index 131ca17..79456b1 100644
> --- a/kernel/irq/handle.c
> +++ b/kernel/irq/handle.c
> @@ -126,7 +126,7 @@ static void irq_wake_thread(struct irq_desc *desc, struct irqaction *action)
> */
> atomic_inc(&desc->threads_active);
>
> - wake_up_process(action->thread);
> + wake_up_handler(action->thread);
wake_up_local() or something more generic than wake_up_handler().
Otherwise looks good.
Thanks,
tglx
next prev parent reply other threads:[~2013-01-14 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 12:10 Alexander Gordeev
2013-01-14 11:19 ` Thomas Gleixner [this message]
2013-01-14 14:11 ` [PATCH v2 " Alexander Gordeev
2013-02-14 14:37 ` Alexander Gordeev
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=alpine.LFD.2.02.1301141217300.7475@ionos \
--to=tglx@linutronix.de \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=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
all inboxes | Powered by JetHome®