Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1816025rwd; Thu, 25 May 2023 19:27:33 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4VRX6VTwrQz/U71QCV0zWtocUqN65l9uu8y1er31sRUjHX8prhA0/F85HAxoOgD7+Xf5b+ X-Received: by 2002:a05:6a20:d045:b0:10b:acb4:620e with SMTP id hv5-20020a056a20d04500b0010bacb4620emr246662pzb.41.1685068052758; Thu, 25 May 2023 19:27:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685068052; cv=none; d=google.com; s=arc-20160816; b=EWLra6DGHjGRUrICD4U407ct92h8CsRjudY+PUxpTF2aRZf+sJqDTe7evO7LpLNMM6 UYqp1lt08q01ucP9saOzyw45raaDcXqorBdUlgoWpk1UzNfXPlhPGmDCMgsPKTNwSMHw NXEI9Kt1O1QsxLiVgVG0bIrBkjN9KlC3YcvPqfv3hKFCzYcj5dGCIoocutsMn+y1vVsJ hBRWpOeYj7+wPHeOKrNp1lx6sh1ogys860dKIpIbz2Xu5BDqwZvVkt4ZbqcroNbNxCUb EHNaCZXPeYY/viAOkQoglXdvq1vf4HO7CCra1H6edYPYcMK1RN2qMMU+KnhTjGwrmPh8 Z1Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=QRIhUR+oTuFzicj0A9tTt5U7sXcp4Ft2BenovbdFSYY=; b=otSZ4Z368a175p/cHxTwVGnWGXrYjYMxiiPPoieot+MG5Cc/Iw9u3zMjZPjmj4GqFd JARrWJ4kHX21tFadiMIHvDNsvtYoTPb8pE9EyH+4EGcsbU8lISzz0HA9yyju6NVOw7rx HjEa0XllMU3ZUXcOEmj6Wh0+1X4dsWo/n5FtK10LAH3RAztsrNdahiAbROm1Og1iYmHJ ZjX5pLa9yLul3vayw+pdrzDpyTRVr8Sit5d+9uzQb/d+EQXOJUQSiy//RKkfecVFBT6U SboYX9ABfMSc5giSRa/q0tQJlvHP7GGVPBbp7KAz1Q1EHzDGL8nLr4mk6Cfyrb16Pd2l WZUg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=b9b5Vz4N; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x24-20020a63db58000000b0051b53285341si2615672pgi.277.2023.05.25.19.27.17; Thu, 25 May 2023 19:27:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=b9b5Vz4N; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230103AbjEZCVD (ORCPT + 99 others); Thu, 25 May 2023 22:21:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51110 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229567AbjEZCVC (ORCPT ); Thu, 25 May 2023 22:21:02 -0400 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 647C21A4 for ; Thu, 25 May 2023 19:20:54 -0700 (PDT) Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1b00ecabdf2so2479215ad.2 for ; Thu, 25 May 2023 19:20:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685067654; x=1687659654; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QRIhUR+oTuFzicj0A9tTt5U7sXcp4Ft2BenovbdFSYY=; b=b9b5Vz4NA+ou0L4F1w4MxfO5cZLFEG7HNxHx8qLvqjqv9XWEccnmQXdGvPHVTez9zZ FxfhmwUloCdF58SRzGhb3Zm7KxwLsh+tAU3zR1C8ZgzDHqme//knfdkHyWHYvIXBXj9+ HyVz3yL4inYXfIFHSJFKezFk9Ep10SXPRWeNmz+4jI3TWgGD9/EdfwtNZSGtWegTyUS5 JrHp8kvQ3S1rRRRlJo0QJiLkvru+pL6nRJEX65UKsLMP1YzAA/P33YPszEB94vVDlutD Nn3cw1UA7nSHONd242Z7jWMbdG1GrFLz42c5YOCm3XUw3MD0iFs93NgieiWc6LsAN5pp lpQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685067654; x=1687659654; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QRIhUR+oTuFzicj0A9tTt5U7sXcp4Ft2BenovbdFSYY=; b=RaO4hdUAFI3i2MQc3p4Xp3V2S4VjUWiUraI88u6plSB6jElXsSbg05zIabt62+oNGX /lIhcN2saOUMIi258pSAPOFTnyRISP86+Fn/mFQleSX8QLWr4s5IfyqrZRY9RhfLMaX/ KbyIWZY+h9V2oUxld4i1s4bjUNPeIHreP+RRznVkuM6MKkb0EU8zV8fSWSIRjGDGrZvO RYKyHh2fVMe0ygk+szsEHnAmQZ+lrcBZjlyPwUtCYeJDOwfEoPJ8ggcumXvkFKG3Nq31 NjLDwNCDihFrAzeND5Q+d8m2YXRaokGLV+aKluK6lMRoLP28O8t+mecigBuZ11Fax65+ rXOQ== X-Gm-Message-State: AC+VfDxLKOhA+IHVbOPOEnnqvU+/ihNgowuPkU6QRwBcPtuXwaR7Q0Cz S6tni7aR37hhJbeOz16lzUM3cMlpxlh+34v/4ArE+vFp9iURHF7S X-Received: by 2002:a17:903:32ca:b0:1b0:1095:f4f6 with SMTP id i10-20020a17090332ca00b001b01095f4f6mr484109plr.24.1685067653787; Thu, 25 May 2023 19:20:53 -0700 (PDT) MIME-Version: 1.0 References: <20230525040038.12346-1-qiang.zhang1211@gmail.com> In-Reply-To: From: Z qiang Date: Fri, 26 May 2023 10:20:42 +0800 Message-ID: Subject: Re: [PATCH v2] workqueue: Do not set CPU_INTENSIVE worker flags with wq_cpu_intensive_thresh_us=0 To: Tejun Heo Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Hello, > > I rewrote the patch description and separated it out into a separate if > statement for readability. Applied to wq/for-6.5. > > Thanks. > > From 18c8ae813156a6855f026de80fffb91e1a28ab3d Mon Sep 17 00:00:00 2001 > From: Zqiang > Date: Thu, 25 May 2023 12:00:38 +0800 > Subject: [PATCH] workqueue: Disable per-cpu CPU hog detection when > wq_cpu_intensive_thresh_us is 0 > > If workqueue.cpu_intensive_thresh_us is set to 0, the detection mechanism > for CPU-hogging per-cpu work item will keep triggering spuriously: > > workqueue: process_srcu hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND > workqueue: gc_worker hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND > workqueue: gc_worker hogged CPU for >0us 8 times, consider switching to WQ_UNBOUND > workqueue: wait_rcu_exp_gp hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND > workqueue: kfree_rcu_monitor hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND > workqueue: kfree_rcu_monitor hogged CPU for >0us 8 times, consider switching to WQ_UNBOUND > workqueue: reg_todo hogged CPU for >0us 4 times, consider switching to WQ_UNBOUND > > This commit therefore disables the CPU-hog detection mechanism when > workqueue.cpu_intensive_thresh_us is set to 0. > > tj: Patch description updated and the condition check on > cpu_intensive_thresh_us separated into a separate if statement for > readability. > > Signed-off-by: Zqiang > > Can you please use your full name as in "FIRST_NAME LAST_NAME " when > signing-off patches in the future? > Because there are many people with the same name as me, so I use the abbreviation of the name to distinguish, but in the future I will use the full name :) . Thanks Zqiang > > Thanks. > > -- > tejun