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 B3466C433EF for ; Fri, 27 May 2022 12:58:33 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 4A80D8D000F; Fri, 27 May 2022 08:58:33 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 4540C8D000C; Fri, 27 May 2022 08:58:33 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3413F8D000F; Fri, 27 May 2022 08:58:33 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 26EAE8D000C for ; Fri, 27 May 2022 08:58:33 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id EE61335522 for ; Fri, 27 May 2022 12:58:32 +0000 (UTC) X-FDA: 79511526864.20.7C741FA Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38]) by imf16.hostedemail.com (Postfix) with ESMTP id 57C68180054 for ; Fri, 27 May 2022 12:58:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1653656312; x=1685192312; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=c4DoNV38Cri5OuSzqTtO0H0lXFQHkPSGKbQ/CIAOqDE=; b=RLBHCkrkPxElVLaOKJbixmDRHyMiKEo6+3CSQlgc8gz68jQdR8MQAifd /rYCk6RAsxKwm8C/YtDAEAG964uqEBjpBNha/oY/WQ5ene8Cx1ldkKfFe fZbRwI1BBoarfPihiAdH3gnHH37fDiOoRZqAaUPm2N6u3FneHxn8VvyNQ A=; Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-01.qualcomm.com with ESMTP; 27 May 2022 05:58:31 -0700 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 May 2022 05:58:30 -0700 Received: from nalasex01a.na.qualcomm.com (10.47.209.196) by nasanex01c.na.qualcomm.com (10.47.97.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Fri, 27 May 2022 05:58:30 -0700 Received: from qian (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Fri, 27 May 2022 05:58:28 -0700 Date: Fri, 27 May 2022 08:58:26 -0400 From: Qian Cai To: Mel Gorman CC: Andrew Morton , Nicolas Saenz Julienne , Marcelo Tosatti , Vlastimil Babka , Michal Hocko , LKML , Linux-MM Subject: Re: [PATCH 0/6] Drain remote per-cpu directly v3 Message-ID: References: <20220512085043.5234-1-mgorman@techsingularity.net> <20220527083946.GF3441@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20220527083946.GF3441@techsingularity.net> X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01a.na.qualcomm.com (10.47.209.196) X-Stat-Signature: bzmb5xs68emm4bfow4a4gptji7nxcm7f X-Rspam-User: Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=quicinc.com header.s=qcdkim header.b=RLBHCkrk; spf=pass (imf16.hostedemail.com: domain of quic_qiancai@quicinc.com designates 199.106.114.38 as permitted sender) smtp.mailfrom=quic_qiancai@quicinc.com; dmarc=pass (policy=none) header.from=quicinc.com X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 57C68180054 X-HE-Tag: 1653656297-285960 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 Fri, May 27, 2022 at 09:39:46AM +0100, Mel Gorman wrote: > Do you think it's related to the series and if so why? From the warning, > it's not obvious to me why it would be given that it's a warning about a > task not being inactive when it is expected to be. I don't know. I just saw the 6/6 patch touched the mm_percpu_wq. Anyway, I'll spend more time to reproduce, and see if we are lucky.