From: Steven Rostedt <rostedt@goodmis.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Alan Stern <stern@rowland.harvard.edu>,
Ming Lei <ming.lei@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
Sebastian Sewior <bigeasy@linutronix.de>
Subject: Re: High-priority softirqs [was: [PATCH] usb: don't offload isochronous urb completions to ksoftirq]
Date: Fri, 15 Jun 2018 17:13:29 -0400 [thread overview]
Message-ID: <20180615171329.05f7e4de@vmware.local.home> (raw)
In-Reply-To: <alpine.LRH.2.02.1806151658000.24974@file01.intranet.prod.int.rdu2.redhat.com>
On Fri, 15 Jun 2018 17:05:01 -0400 (EDT)
Mikulas Patocka <mpatocka@redhat.com> wrote:
> I don't think that threaded interrupt handlers are a good idea.
>
> There are existing tools such as rtkit in Linux distributions that
> increase the priority of audio applications to real time. And if rtkit
> increases the priority of audio player or audio server above the priority
> of the interrupt thread that handles the soundcard - sound playback is
> screwed.
>
> You would have to set the priority of the interrupt thread to the highest
> real-time priority - and in such a case, the interrupt thread is no
> different than a hard-irq handler.
Perhaps rtkit et.al. should be updated to know about interrupt threads.
It's pretty trivial to know about them and that can easily be
automated. The only problem is to keep the irq thread higher than the
audio server. And we always tell people to never put a thread to the
maximum priority unless they had a damn good reason to do so.
-- Steve
prev parent reply other threads:[~2018-06-15 21:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:29 [PATCH] usb: don't offload isochronous urb completions to ksoftirq Mikulas Patocka
2018-06-12 14:38 ` Alan Stern
2018-06-12 14:44 ` Mikulas Patocka
2018-06-12 15:11 ` Alan Stern
2018-06-12 16:03 ` Mikulas Patocka
2018-06-12 16:38 ` Alan Stern
2018-06-12 17:19 ` Mikulas Patocka
2018-06-12 17:52 ` Greg Kroah-Hartman
2018-06-12 18:50 ` Mikulas Patocka
2018-06-12 18:44 ` Alan Stern
2018-06-12 19:03 ` Mikulas Patocka
2018-06-12 20:06 ` Alan Stern
2018-06-13 13:57 ` Mikulas Patocka
2018-06-13 14:13 ` Alan Stern
2018-06-13 16:35 ` Mikulas Patocka
2018-06-13 18:54 ` Alan Stern
2018-06-13 19:30 ` Mikulas Patocka
2018-06-13 22:31 ` Steven Rostedt
2018-06-14 22:23 ` Mikulas Patocka
2018-06-14 22:35 ` Steven Rostedt
2018-06-15 16:41 ` Mikulas Patocka
2018-06-15 16:46 ` Steven Rostedt
2018-06-15 17:17 ` High-priority softirqs [was: [PATCH] usb: don't offload isochronous urb completions to ksoftirq] Alan Stern
2018-06-15 17:28 ` Thomas Gleixner
2018-06-15 17:34 ` Steven Rostedt
2018-06-15 17:40 ` Sebastian Sewior
2018-06-15 20:54 ` Alan Stern
2018-06-15 21:05 ` Mikulas Patocka
2018-06-15 21:13 ` Steven Rostedt [this message]
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=20180615171329.05f7e4de@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=stern@rowland.harvard.edu \
--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
all inboxes | Powered by JetHome®