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 2DF81C46467 for ; Tue, 10 Jan 2023 15:19:33 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 945DC8E0002; Tue, 10 Jan 2023 10:19:32 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 8CE2A8E0001; Tue, 10 Jan 2023 10:19:32 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 795978E0002; Tue, 10 Jan 2023 10:19:32 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 6534E8E0001 for ; Tue, 10 Jan 2023 10:19:32 -0500 (EST) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 2E230ADF17 for ; Tue, 10 Jan 2023 15:19:32 +0000 (UTC) X-FDA: 80339248584.21.CA570E3 Received: from mail3-166.sinamail.sina.com.cn (mail3-166.sinamail.sina.com.cn [202.108.3.166]) by imf12.hostedemail.com (Postfix) with ESMTP id E6C6840018 for ; Tue, 10 Jan 2023 15:19:18 +0000 (UTC) Authentication-Results: imf12.hostedemail.com; dkim=none; spf=pass (imf12.hostedemail.com: domain of hdanton@sina.com designates 202.108.3.166 as permitted sender) smtp.mailfrom=hdanton@sina.com; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1673363970; 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-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mIujYuMIyFbHcCtok/g2jBlNekBiAgeBFgczdTOsHks=; b=mPWRS6CkxX3adzI0EgbpvQTbqiZnsGwIcWWks/NuKqT4G5qcTndtSioJPWVYCOeETe9gVd LbFKlxQ9G6VtjPMNZ5+pqCP/9Xut3RJ1Pj4rcH0FQiqBmfD8tZ1ebBUAYgv/W4xBddUz/6 Ld46ZCuVSxp18cgZA6svF+ymXPGAXbA= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=none; spf=pass (imf12.hostedemail.com: domain of hdanton@sina.com designates 202.108.3.166 as permitted sender) smtp.mailfrom=hdanton@sina.com; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1673363970; a=rsa-sha256; cv=none; b=M8feN/46d1BPrllbDsWNtLvqmRwAZ2aw4e2nEq3Zv1O8allGoiNgNDJa+CgjZZhflCFFOv sTrxgpD/nzV+LTris4nMG4Oi8N0w1mohwCYVCTb4XKOPZTxT4Td3TCXLDRqsZRPcUZ7i2V xuwfy3iJbu/jIVWG5XA28bxGLnBmK4s= Received: from unknown (HELO localhost.localdomain)([114.249.61.130]) by sina.com (172.16.97.23) with ESMTP id 63BD81390002518F; Tue, 10 Jan 2023 23:16:11 +0800 (CST) X-Sender: hdanton@sina.com X-Auth-ID: hdanton@sina.com X-SMAIL-MID: 43064954920055 From: Hillf Danton To: Marcelo Tosatti Cc: atomlin@atomlin.com, frederic@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v13 3/6] mm/vmstat: manage per-CPU stats from CPU context when NOHZ full Date: Tue, 10 Jan 2023 23:19:01 +0800 Message-Id: <20230110151901.402-1-hdanton@sina.com> In-Reply-To: References: <20230105125218.031928326@redhat.com> <20230106001244.4463-1-hdanton@sina.com> <20230106150154.4560-1-hdanton@sina.com> <20230107001529.4617-1-hdanton@sina.com> <20230110024356.336-1-hdanton@sina.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Stat-Signature: a9g6qt6qpt941jdryeen77hm9kmz6g85 X-Rspam-User: X-Rspamd-Queue-Id: E6C6840018 X-Rspamd-Server: rspam06 X-HE-Tag: 1673363958-836233 X-HE-Meta: U2FsdGVkX1++PCSooS7FtADwfMwmqXwU4jVJ+ld+ksJyd3XyFUmhVBhoa/pBMlU7WcNgVWZISYCy2pofN2jmxh8y+OpQa54b0PiWIBJXd+bYDSKMWFYvVi3/FEQ0f4SE2Zkb+9Fu6kniZd3Pd/Lhzg0KmxyQpWo4fySKBAKQpb/+WktQJq8LddHSAfO6V+B85xBGQZqvVEST+3rHtwm7jGtT6cFPlQvRrjCjafXAnb1iaUiSQlY7JvOy6W2bAgXjlG4zeGIJd5cHBnK1XfMtce2ty0datEpUSe4syl7wSUV57ZuU1a+mYclSj4P/dWxXwOVf0Z2dqzi9C+8XX5J7RBYp83XZe/3Of1e/sFORbOLt5iomOW9ihOrlCeTUe2M5xwroKFfQkhTfpDZ31BduFgVne3Byfeqp6GImwQ4vWI8bzokgMfkujRVFs4gjvCFKJWsL03DjS8AOR7a13Uof1eioV6A29KDJbip9HhiIwxwjsUknawgOWKEvqNYUTr9AGuKY9UsTxKaAVJYjkPfDdAYhj+EcfPJBren3HJx6XxvykUsext8G+iNqZptfQ6EDwEHbCqpUxp3erFQvzT3ymEwph/tnp0mOj7j0vSL040lo7Ey8iF5QzXWjdXDiDjBD+0JaRyqqFGqNewPMkGnLyxXFkI3B6tLtk5Bdz3XjHbvwbsoL0R0Ol1RURX/ileanV/RFskcgTpG5jWDTW2U0C3wbhp/XUKUhP8ytyaQExFie3l0LT/7ohAI8O31+g6K1ycRyoD7DyRYqcE5dYksCWNxyFY2VRNT5VZSgIOWAwGw= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000021, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, 10 Jan 2023 08:50:28 -0300 Marcelo Tosatti > On Tue, Jan 10, 2023 at 10:43:56AM +0800, Hillf Danton wrote: > > On 9 Jan 2023 11:12:49 -0300 Marcelo Tosatti > > > > > > Yes, but if you do not return to userspace, then the per-CPU vm > > > statistics can be dirty indefinitely. > > > > Could you specify the reasons for failing to return to userspace, > > given it is undesired intereference for the shepherd to queue work > > on the isolated CPUs. > > Any system call that takes longer than the threshold to sync vmstats. Which ones? If schedule() occurs during syscall because of acquiring mutex for instance then anything on the isolated runqueue, including workqueue worker shepherd wakes up, can burn CPU cycles without undesired intereference produced. > > Or a long running kernel thread, for example: It is a buggyyyy example. > > https://stackoverflow.com/questions/65111483/long-running-kthread-and-synchronize-net