Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1275066imm; Fri, 15 Jun 2018 14:15:22 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLPORy9nbfRYwBwU/YcUa+4wtufm3Xtr6P7KMQ6NX6Wn8AXVzbz0UhhAGgi4gQm4H14wtZd X-Received: by 2002:a62:1bc2:: with SMTP id b185-v6mr3640942pfb.225.1529097322725; Fri, 15 Jun 2018 14:15:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529097322; cv=none; d=google.com; s=arc-20160816; b=uR+bqjWV8p9zx1BmQGHowDpVTuENrW0nfKBsgZEqwPCV9U9aKXXtcdYfp9jzXkSwCx N3DN5YHDqzrupNfIbcyBDBuYxIybBFxfYr6DwGe1NyVikXUxWCjkvF5jTab8cA2cmU2J n+tZl3MLuNTzwMn8XGzLn+vJ+oU9+RAMcX9LMC85IXITRhAl6POmOAy4xLw4fG5rP5qm 3bdkaDB94hohZKxyuB4yN8zN7rcJYu5R7G8sWGvf0rkBS4A/axH+u+BGz8f4qwMkvvxR y4L+GVcrt2peb43uSzDwJXii5Nqv410BTnoKjRJXEl3xYsepduPZvXkDUgFPA4lH147K tvVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=HNQzrh0Wd80Y53BDLVT0QahKFTeqTe/fSndRmGjWoAA=; b=z/0qeEaCnR0jg1BWddjVITbZuebhOY5ZSvLKmxz7VhvhaE4c7Xb/lsEArIQV00mWPe YTNvimSMKPvS1BCOrktEnlRoj7vV4jSRdmeKjAD98WlWlZFMN4OQ1ULomHVN5Or1A31n ehENUzEMu2yZYEVuS9seSvz3dt8YT4Qd6bKYpHgbXo7GjwzaaBtIQdub5vIDMM7sI8AN qeQl7+h3VVa3NW+L+NVJd42JFk2MQUIJZ7ICyVb8D8FvXBXM2WD4d0e8Pc0DQ4/IDGtA K9PYJwtsp1TWgXN0bzwCahKRxpUxrM31l9ruyTQ8dJAJLfRSCSCaSePp6gm/gZ8xaOKN R4hQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b30-v6si10419962pli.427.2018.06.15.14.15.08; Fri, 15 Jun 2018 14:15:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756580AbeFOVNf (ORCPT + 99 others); Fri, 15 Jun 2018 17:13:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:34508 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756434AbeFOVNd (ORCPT ); Fri, 15 Jun 2018 17:13:33 -0400 Received: from vmware.local.home (user-0cemj78.cable.mindspring.com [24.235.76.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 467EF20896; Fri, 15 Jun 2018 21:13:32 +0000 (UTC) Date: Fri, 15 Jun 2018 17:13:29 -0400 From: Steven Rostedt To: Mikulas Patocka Cc: Thomas Gleixner , Alan Stern , Ming Lei , Greg Kroah-Hartman , USB list , Kernel development list , Sebastian Sewior Subject: Re: High-priority softirqs [was: [PATCH] usb: don't offload isochronous urb completions to ksoftirq] Message-ID: <20180615171329.05f7e4de@vmware.local.home> In-Reply-To: References: X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 15 Jun 2018 17:05:01 -0400 (EDT) Mikulas Patocka 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