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 A8621C32771 for ; Mon, 26 Sep 2022 12:53:28 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E5BB08E0043; Mon, 26 Sep 2022 08:53:27 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E0A9B8E0039; Mon, 26 Sep 2022 08:53:27 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CABF68E0043; Mon, 26 Sep 2022 08:53:27 -0400 (EDT) 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 BC9EC8E0039 for ; Mon, 26 Sep 2022 08:53:27 -0400 (EDT) Received: from smtpin18.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 5B11280B0F for ; Mon, 26 Sep 2022 12:53:27 +0000 (UTC) X-FDA: 79954227654.18.0D0B31B Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) by imf19.hostedemail.com (Postfix) with ESMTP id 052941A000A for ; Mon, 26 Sep 2022 12:53:25 +0000 (UTC) Received: by mail-pg1-f177.google.com with SMTP id bh13so6469791pgb.4 for ; Mon, 26 Sep 2022 05:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date; bh=JfI/MQ3cqMqiBUWply4+srFdGKgWiHs9QbzXGnedrjw=; b=py/jOoP+LNdmJsrwUiecLbM+RTy9qdwEEAUALnxViUcmpv12jPLZ1j8G3Pfx7DLDqV K99WGoTIFAGynejfWry3s0e5BHXkn0fc2ohyqEpW0Evq54sfrnUjTnwSrmsvgRz+BRqo k/Lzkdml0LQ6B0ieqaNEV73WkMwrBW4yi/P9OYlCbEW6X3FUNcd3N4VpE2fdgeEXPM70 JpCnbC5hJuxY73hbCc6CnKtUyCoyoBco8sXVwsObAYGR/2GGLe4ZcYGdFRSYrxpyLa35 z32e9L5Ukv6DsMO6XpMMJErLNKv9h9nndfxOliXE3TUOnAE9XbqHiG2IoRhKG0sJfqOF zYKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date; bh=JfI/MQ3cqMqiBUWply4+srFdGKgWiHs9QbzXGnedrjw=; b=hxuz+WxqYedg44YtST2WN/0KtW0hvEXsTS9wLLhigICwQX9t8GztS/yiXgecuMnTEE q+gekqKik+EBnI3Sf4VvcGCacLNSWjHojM/67HAy6bnoFDbnlRTNDBAckn4BFxMjY2ph o6qjqMQbVIgbR4TV4jb30L3bCCWYEMuLe3c8Hhhmff+yae0rLbYQuQ0bAc2+dZLddOxR ZLEM/pIT1wQvIZe+l5HBvLV96hgMUSFzAU1MTytS6rnQXRN/8ivuIgdBWuQ85aM9xZPU QKKC9X/KWfb2ooksl599E560gCbojODU5HvYvvx1clPq2+psbbRmkh5lqz0XDoEB42E1 ofqA== X-Gm-Message-State: ACrzQf3uMB5aUcWucwhu371s0zZa3yy7vHAa5g/6vd6+S6nlbRAiYMi5 +o3A+yB1ceM5fgAcB3jxkwy1Lw== X-Google-Smtp-Source: AMsMyM4pRwA8C32gEkFcBudu2gl4n1YxKWuI7PaQvRSdl0XKQx52Sa6xuC252+HH/8g8/i7QCjy3LA== X-Received: by 2002:a62:6085:0:b0:53e:7874:5067 with SMTP id u127-20020a626085000000b0053e78745067mr23937829pfb.4.1664196804856; Mon, 26 Sep 2022 05:53:24 -0700 (PDT) Received: from [10.68.76.92] ([139.177.225.245]) by smtp.gmail.com with ESMTPSA id q20-20020aa78434000000b0053fcb800ec0sm12107196pfn.9.2022.09.26.05.53.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Sep 2022 05:53:24 -0700 (PDT) Message-ID: <24b20953-eca9-eef7-8e60-301080a17d2d@bytedance.com> Date: Mon, 26 Sep 2022 20:53:19 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: [External] Re: [RFC] proc: Add a new isolated /proc/pid/mempolicy type. To: Michal Hocko Cc: corbet@lwn.net, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, wuyun.abel@bytedance.com References: <20220926091033.340-1-hezhongkun.hzk@bytedance.com> From: Zhongkun He In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b="py/jOoP+"; spf=pass (imf19.hostedemail.com: domain of hezhongkun.hzk@bytedance.com designates 209.85.215.177 as permitted sender) smtp.mailfrom=hezhongkun.hzk@bytedance.com; dmarc=pass (policy=none) header.from=bytedance.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664196807; a=rsa-sha256; cv=none; b=CRIVhPFZvmw5SZ19/fGBKefbHKXJeEZxkafKWYz8aSdKqJSEeynKzy405PR87poe4DDk8a tMHWjgdsbt/Chu11IJ9mWsvtzioLvEYpUtws1UqIULcHE5QYDkJh7Vl44UF3HF+RYz2V1C cHiiP/X77EK3mSSrlyNboSjf9QTEXw0= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664196807; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=JfI/MQ3cqMqiBUWply4+srFdGKgWiHs9QbzXGnedrjw=; b=kwazFi33J9+Q0BVeyjg1OMWAqui1FypiFB02nlfR4ypJNms6in2aLmXbsUsEeuvU8Ilaul 2kpNbbnWwMFqB0jCUu/WVB4z+2E5HNmvZ2ZkTkhbTJhpsx7Rdk6jmOsWPooUq0Jg1FCKaz yA3P22IuF2E8BVyRxbWMCjnYtijoUZs= X-Stat-Signature: 1aai9nju1fjausqmfpwdo7kji6oqieme X-Rspamd-Queue-Id: 052941A000A Authentication-Results: imf19.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b="py/jOoP+"; spf=pass (imf19.hostedemail.com: domain of hezhongkun.hzk@bytedance.com designates 209.85.215.177 as permitted sender) smtp.mailfrom=hezhongkun.hzk@bytedance.com; dmarc=pass (policy=none) header.from=bytedance.com X-Rspam-User: X-Rspamd-Server: rspam03 X-HE-Tag: 1664196805-481051 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: > [Cc linux-api - please do so for any patches making/updating > kernel<->user interfaces] > > > On Mon 26-09-22 17:10:33, hezhongkun wrote: >> From: Zhongkun He >> >> /proc/pid/mempolicy can be used to check and adjust the userspace task's >> mempolicy dynamically.In many case, the application and the control plane >> are two separate systems. When the application is created, it doesn't know >> how to use memory, and it doesn't care. The control plane will decide the >> memory usage policy based on different reasons.In that case, we can >> dynamically adjust the mempolicy using /proc/pid/mempolicy interface. > > Is there any reason to make it procfs interface rather than pidfd one? Hi michal, thanks for your reply. I just think that it is easy to display and adjust the mempolicy using procfs. But it may not be suitable, I will send a pidfd_set_mempolicy patch later. Btw.in order to add per-thread-group mempolicy, is it possible to add mempolicy in mm_struct?