[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180615171329.05f7e4de@vmware.local.home>
Date: Fri, 15 Jun 2018 17:13:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mikulas Patocka <mpatocka@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Alan Stern <stern@...land.harvard.edu>,
Ming Lei <ming.lei@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
Sebastian Sewior <bigeasy@...utronix.de>
Subject: Re: High-priority softirqs [was: [PATCH] usb: don't offload
isochronous urb completions to ksoftirq]
On Fri, 15 Jun 2018 17:05:01 -0400 (EDT)
Mikulas Patocka <mpatocka@...hat.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
Powered by blists - more mailing lists