Received: by 10.223.176.46 with SMTP id f43csp4519330wra; Tue, 23 Jan 2018 10:25:33 -0800 (PST) X-Google-Smtp-Source: AH8x227SSMGtlEz1c/s8H3S4EuckRkdjJnGJWrGzf3xdlvwYCNLhUEosOX4qhT+DpAZJJFMCErGu X-Received: by 10.107.12.224 with SMTP id 93mr4969258iom.48.1516731932928; Tue, 23 Jan 2018 10:25:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516731932; cv=none; d=google.com; s=arc-20160816; b=D+5+H7jhTL/5B9pwp1Qn0BeCvEJpffuvbqelU6qr3drdfdhROXqw/A4Jyp+aQas23o GuQO0CSeYCodTHvzBwOFKgZsTHGc4pdnrCuKbXQ3M01H2he1jpTxPXZAp+G41F8sKr7b iwWhhjgeHNp8Bu/qvmFbPVnUYgSjGf8OD8/0jLY5zBfsxpy/CJsqQxrIIqmhsbBF/sJC w4Yfmy6t6vmy+6KMLiN+frlPsf+YBRaP5Tt/td56/LVq62empjhNPOmCYM0yJXi33aS8 +NiLEoRcoZUo732QPBscHhMx4tLqwQK+fWA7rewJOWSyzaaBTU2CPsBbebSynab1suty fxQg== 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:from:subject:cc:to:message-id:date :arc-authentication-results; bh=3Btxr+n8xvBUB+A2zxDm0xep3w5pxwv9bKU6MvEaxZQ=; b=NatWoZpeEkZ2ipoZUok+GRx3PQFBMJnwwZq9KsXZ62W0RdHRgT+Z1L6BabmILH6cUo 2hZr8ctBew+JKXGWBvyvXSUImGvDTzrSPBoGwmQn/K4pu31qXQY0OnBaqckB2VlRlU/B h7eGLGIVLYf+ssBcN8YMFIbDQ6BtdWTcNw+QmQAJgI9gXSsC3PZ6OqZ4KE15REeAeqjT LDoSeQITJqrHNWnymsNdlyEdNSeD12U0fl+xp3meQ+GpBNarJ/lReDDOcJ+CsS/0Asp2 rFeLa9o29QG3VfX76LXZrVbM3uKa6i0UgVHZGCMbgdGC7zPzuAUSkeaZ6b+EnWQA14sO 3L7Q== 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 e30si8195080ioj.36.2018.01.23.10.25.19; Tue, 23 Jan 2018 10:25:32 -0800 (PST) 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 S1752082AbeAWSY3 (ORCPT + 99 others); Tue, 23 Jan 2018 13:24:29 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:57284 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbeAWSY3 (ORCPT ); Tue, 23 Jan 2018 13:24:29 -0500 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id B7FFD100A6CD3; Tue, 23 Jan 2018 10:24:26 -0800 (PST) Date: Tue, 23 Jan 2018 13:24:24 -0500 (EST) Message-Id: <20180123.132424.1035340800864767853.davem@davemloft.net> To: torvalds@linux-foundation.org Cc: pabeni@redhat.com, frederic@kernel.org, linux-kernel@vger.kernel.org, alexander.levin@verizon.com, peterz@infradead.org, mchehab@s-opensource.com, hannes@stressinduktion.org, paulmck@linux.vnet.ibm.com, wanpeng.li@hotmail.com, dima@arista.com, tglx@linutronix.de, akpm@linux-foundation.org, rrendec@arista.com, mingo@kernel.org, sgruszka@redhat.com, riel@redhat.com, edumazet@google.com Subject: Re: [RFC PATCH 0/4] softirq: Per vector threading v3 From: David Miller In-Reply-To: References: <20180123.112201.1263563609292212852.davem@davemloft.net> <1516726652.2554.58.camel@redhat.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 23 Jan 2018 10:24:28 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Linus Torvalds Date: Tue, 23 Jan 2018 09:42:32 -0800 > But I wonder if the test triggers the "lets run lots of workqueue > threads", and then the single-threaded user space just gets blown out > of the water by many kernel threads. Each thread gets its own "fair" > amount of CPU, but.. If a single cpu's softirq deferral can end up running on multiple workqueue threads, indeed that's a serious problem. So if we're in a workqueue and it does a: schedule_work_on(this_cpu, currently_executing_work); it'll potentially make a new thread? That's exactly the code path that will get exercised during a UDP flood the way that vector_work_func() is implemented.