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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE1D6C433EF for ; Fri, 27 May 2022 12:58:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351147AbiE0M6f (ORCPT ); Fri, 27 May 2022 08:58:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40836 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348628AbiE0M6c (ORCPT ); Fri, 27 May 2022 08:58:32 -0400 Received: from alexa-out-sd-02.qualcomm.com (alexa-out-sd-02.qualcomm.com [199.106.114.39]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C445830F5C for ; Fri, 27 May 2022 05:58:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1653656311; x=1685192311; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=c4DoNV38Cri5OuSzqTtO0H0lXFQHkPSGKbQ/CIAOqDE=; b=mOn+rTUVHn0Mqn7MzUiORxcuhqRx8L/H8nUBvk0b7kFCm++fMPAtcpcS 6dO0InLsT74YiUoDnzfEJEDeH3cZFoQv8dN3FoYydbEULfBRY0KLvdQMJ ap9gTivcNNd3faI052jT6OjKFR0hMgPETqEXiGgg7lblriuur0zkffVMH 0=; Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-02.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) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.