From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Mikulas Patocka <mpatocka@redhat.com>,
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 13:34:28 -0400 [thread overview]
Message-ID: <20180615133428.20205bae@gandalf.local.home> (raw)
In-Reply-To: <alpine.DEB.2.21.1806151919130.1582@nanos.tec.linutronix.de>
On Fri, 15 Jun 2018 19:28:34 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:
> One solution to that is to avoid both tasklets and kworkers and change the
> USB code to make use of threaded interrupt handlers. I.e. handle the fast
> stuff in the primary (hardirq) handler and delegate the rest to the irq
> thread. That thread still can offload disk type stuff to a kworker if
> needed. But the irq thread allows to bring the stuff under scheduler
> control and experiments which I did a few years ago worked out pretty good.
If there's any question about this, drivers can request to have their
interrupt handlers run as threads. This has been added to mainline
years ago. And it really should be the default solution before pushing
off to tasklets or kworkers.
-- Steve
next prev parent reply other threads:[~2018-06-15 17:34 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 [this message]
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
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=20180615133428.20205bae@gandalf.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®