Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965117AbeALRvp (ORCPT + 1 other); Fri, 12 Jan 2018 12:51:45 -0500 Received: from mail-io0-f171.google.com ([209.85.223.171]:39766 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964844AbeALRvo (ORCPT ); Fri, 12 Jan 2018 12:51:44 -0500 X-Google-Smtp-Source: ACJfBosaCjGsQhApZFerSo9yPbAUiNVZ5rN6EZ+fBdYajAgiiAEtkPzk6vV5wOETlNVPFY4E/Hu9r9U4/96CHGy/ODU= MIME-Version: 1.0 In-Reply-To: <1515779049.21898.23.camel@gmx.de> References: <20180111163204.GE6176@hirez.programming.kicks-ass.net> <1515734588.10188.36.camel@gmx.de> <20180112101336.GT3040@hirez.programming.kicks-ass.net> <1515779049.21898.23.camel@gmx.de> From: Linus Torvalds Date: Fri, 12 Jan 2018 09:51:42 -0800 X-Google-Sender-Auth: WScnytPaDepP4pz3d80l6WOxE9c Message-ID: Subject: Re: [RFC 1/2] softirq: Defer net rx/tx processing to ksoftirqd context To: Mike Galbraith Cc: Peter Zijlstra , Eric Dumazet , Dmitry Safonov , Frederic Weisbecker , LKML , Dmitry Safonov <0x7f454c46@gmail.com>, Andrew Morton , David Miller , Frederic Weisbecker , Hannes Frederic Sowa , Ingo Molnar , "Levin, Alexander (Sasha Levin)" , Paolo Abeni , "Paul E. McKenney" , Radu Rendec , Rik van Riel , Stanislaw Gruszka , Thomas Gleixner , Wanpeng Li Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Fri, Jan 12, 2018 at 9:44 AM, Mike Galbraith wrote: > > Nah, a misunderstanding happened. RT that still offers full threading > creates per-softirq threads per cpu. The regular trees split ksoftirqd > into only two threads per cpu, one processes timer/hrtimer softriqs, > the other processes the rest. Ok, that sounds like it should work, but it also sounds like it's very specific to RT itself. For example, the dvb issue was not about the timer softirqs, but about the tasklet ones. So maybe we wouldn't need to split it for _every_ softirq, but we'd need to split it more than just along the timer case. And it does sound a bit excessive to have ten fixed threads for every CPU. The days when tens of CPU's meant "huge system" are gone. These days it can be a phone. Linus