From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0EF58C433FE for ; Wed, 5 Oct 2022 01:14:07 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 659986B0072; Tue, 4 Oct 2022 21:14:07 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5E33E6B0073; Tue, 4 Oct 2022 21:14:07 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 482FD6B0074; Tue, 4 Oct 2022 21:14:07 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 31A556B0072 for ; Tue, 4 Oct 2022 21:14:07 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id F052E160326 for ; Wed, 5 Oct 2022 01:14:06 +0000 (UTC) X-FDA: 79985124492.11.39CA4AA Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) by imf02.hostedemail.com (Postfix) with ESMTP id 94E4680019 for ; Wed, 5 Oct 2022 01:14:06 +0000 (UTC) Received: by mail-lj1-f172.google.com with SMTP id p5so17127790ljc.13 for ; Tue, 04 Oct 2022 18:14:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=ugwHEDQcF5VRN+4KCFZX1pbxbkZuWcWFPr79Ra+qDPI=; b=do+K2FKZlQ8TcKuvbRmDV+wUmqtG+O9ZHQ2AQs80qmIOF3Ndf/etuoxrXAtnR88Eky Ft1R3yunWStcGdXxedW6H3WxHi7Y/2LcCbQoKVvy910dO/gFWuk09itNyafbYYHEYC2n hpmlzZ172XZrdr7jpolEGuLd+0r3msrP3beff5UUfYD5WagkVQo3jjYD6tbqOdDp9OUP 3Icyu2nnxdmoT3XRlHybLzEv+A90HjV9D8HnSjYVUyPSQCBJGcl6DvmjsKEtJdo594RP 22ang0YRM72WZA/Yc+gPeJGqoMiOpNxSRfYSJmOyFPN8Bx7/oYERIqIIPKQRWEZ0Cu/K 6BhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=ugwHEDQcF5VRN+4KCFZX1pbxbkZuWcWFPr79Ra+qDPI=; b=gCDUyuNVxglW2PXBbJKwCkyl7wp8YG7uliWFFvzXSDSgryb+beS1v1oLYcpGSVJ00J DkYQODH6YsA2n7GH0mVllALeP0cDv+kBVwMUpwb8KGcdVQV8+dIXvHJX9zjOqoFBI64a sK3IxxvIVkN24mYVYlYXj/KhRUAxT5YbTTSKc+risPMzLne746rSVz0Qa7tWkYYzG0Lg gM2od0aGAOTi5jzcg0GYOAJlHutOn/TQ1uYNO5IzknOdnLdxo7bfUHJgmeCV/Icg4JY3 UcqbzeX7yGvzJoKr3r3Sk2TiIvdk+0bt450OOlGRJZ+kVZpBaUm/QMN7z6TjuEyagy/p Tnrg== X-Gm-Message-State: ACrzQf2rWUh0tbbYYs/AyIdrplYaOHWL2x1gz7OaUPtyxbAwSzpI8bOZ pNY0LIL3i+T1p8hCV87gQRj052R1dCIGJEyx+eoB X-Google-Smtp-Source: AMsMyM4uwwNWAHUFkjOS8v4YCZr/nXwvqOlu921focmmgXpukWXHI/nXVpmmvFWPQ6QMi+fqImbpRUlKbxeRCgv7BC8= X-Received: by 2002:a05:651c:1546:b0:26d:9459:1a69 with SMTP id y6-20020a05651c154600b0026d94591a69mr9827913ljp.209.1664932444752; Tue, 04 Oct 2022 18:14:04 -0700 (PDT) MIME-Version: 1.0 References: <20221003232033.3404802-3-jstultz@google.com> <20221004013611.1822-1-hdanton@sina.com> <20221005002149.1876-1-hdanton@sina.com> In-Reply-To: <20221005002149.1876-1-hdanton@sina.com> From: John Stultz Date: Tue, 4 Oct 2022 18:13:52 -0700 Message-ID: Subject: Re: [RFC PATCH v4 2/3] sched: Avoid placing RT threads on cores handling long softirqs To: Hillf Danton Cc: LKML , linux-mm@kvack.org, "Connor O'Brien" , Qais Yousef , Peter Zijlstra , Steven Rostedt Content-Type: text/plain; charset="UTF-8" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664932446; a=rsa-sha256; cv=none; b=Wk2aPH473ZOgzbAPTU/wCi+ckJnm+ImshyeVfoNwO3F4EB7CSjqQff/lQMGHspKfA+8S/Z zSiQZzkaBSiQxYWACzzzfodXfW9+a8LP+KzViaSeDV5TfC/erbKwlag9XwOCxQ+IAHH905 dHWUu6QJZa1xgmOzFoV8474yJAOWR04= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=do+K2FKZ; spf=pass (imf02.hostedemail.com: domain of jstultz@google.com designates 209.85.208.172 as permitted sender) smtp.mailfrom=jstultz@google.com; dmarc=pass (policy=reject) header.from=google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664932446; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=ugwHEDQcF5VRN+4KCFZX1pbxbkZuWcWFPr79Ra+qDPI=; b=HFDaSx/evxEEpyaxp1u2lx2T+/ThJNPZxj+CXMICa/Qbv0qbET9qmM+SPKwatchF95WiOK 4Gf835WR3gp1PCfaSEe1T3LnyHeuQIP0Qad25QyJazInsHvRQEaPWfpkEq9OE2jRts94+A a7BvPR2uc9FkBOox4buei9I92Q3QPtI= X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 94E4680019 X-Rspam-User: Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=do+K2FKZ; spf=pass (imf02.hostedemail.com: domain of jstultz@google.com designates 209.85.208.172 as permitted sender) smtp.mailfrom=jstultz@google.com; dmarc=pass (policy=reject) header.from=google.com X-Stat-Signature: 5smbhzrgzwb1nyas1gjjmpcbazjeuetz X-HE-Tag: 1664932446-718971 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Oct 4, 2022 at 5:22 PM Hillf Danton wrote: > On 3 Oct 2022 19:29:36 -0700 John Stultz > > > > Why would ksoftirqd preempt the rt task? > > > For example the kthread becomes sensitive to latency. Again, my apologies, I'm still not sure I am following. Could you expand a bit on the case you're concerned about? Is it the case where the ksoftirqd thread is configured to run at higher rtprio? thanks -john