Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp369318imj; Sat, 16 Feb 2019 02:08:58 -0800 (PST) X-Google-Smtp-Source: AHgI3Ibz0blFP4auPbjX1pGPo/WIIx3eb7gOp+yCzlmz0yOudrG+2ASGhq81AWDbTSCGxIxiLTEy X-Received: by 2002:a62:5003:: with SMTP id e3mr14533611pfb.23.1550311738203; Sat, 16 Feb 2019 02:08:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550311738; cv=none; d=google.com; s=arc-20160816; b=lhAWe7PsNxjTdwoDFm/bW08/Gm/uVMLWwFWFQSB5GQa6qvbU3MIhSYHXxgZZBOlvsj wDRAG/0E9mZafFK4qYgGNBEGI+JOBmydYpWahXWdwhNH3zgkHgG55w9Al4LMvY0pXEZS FqZtVn9m1ZGf+Yg2SyU35x5qZg50vD81QIqjSsXyUo0BdLbquXH26/s20uebYrV9yiJ5 cWD0LVZ0y17jA/TwoyIhYRIO/lqsa7ed+aSnQHOOaFpWUtYBBtndk8SUI6TG0fbWTzAR /wv/YagfynEtD+7jEHUz2xz9hKkjqt/+KeVu9vzdZCjQXdZLIfIK9aexNtJS/fYbocfK 18pA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=2N2EWSe2QIjfFUIlI7BzyvrKm4weSNV599whd376Ke4=; b=OCgXpU6LzJkPnoq08e4XovtEQjxMCPciKIY8EkzzFM2LiI6fU96E90vf1SuDGCs3hP m0NH3gqOUa/MUPLsbH/pqDyqNwN+Vw/iVOL0vmDiGVGYVbU4/Jne4X/BKN/ATdW/n5Dr 0GEEhvj0FSGHI+JAb4o4CX74Ztr0OKh/LndxkzVaeHCuAsD9/HP8OOv13r5t16/BW6y5 1YzBA+lKKyGKxx1VclwzL+Sv0EYqKA3Xgb9xAar9DeT5zm8gPJsy/o91P4EvYF9jeJXQ /cwQvhE06gPpsv0oHcf63XKz6nxt2jdsvW/X4mqjtMHokCKUmBZXiADfcMFKTZbuQTXz Fz2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id az9si7702292plb.276.2019.02.16.02.08.42; Sat, 16 Feb 2019 02:08:58 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730497AbfBPA4S (ORCPT + 99 others); Fri, 15 Feb 2019 19:56:18 -0500 Received: from out30-44.freemail.mail.aliyun.com ([115.124.30.44]:55344 "EHLO out30-44.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726874AbfBPA4S (ORCPT ); Fri, 15 Feb 2019 19:56:18 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R181e4;CH=green;DM=||false|;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e01424;MF=yang.shi@linux.alibaba.com;NM=1;PH=DS;RN=7;SR=0;TI=SMTPD_---0TKBzhpr_1550278564; Received: from e19h19392.et15sqa.tbsite.net(mailfrom:yang.shi@linux.alibaba.com fp:SMTPD_---0TKBzhpr_1550278564) by smtp.aliyun-inc.com(127.0.0.1); Sat, 16 Feb 2019 08:56:15 +0800 From: Yang Shi To: tj@kernel.org, hannes@cmpxchg.org, corbet@lwn.net Cc: yang.shi@linux.alibaba.com, cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [PATCH] doc: cgroup: correct the wrong information about measure of memory pressure Date: Sat, 16 Feb 2019 08:56:04 +0800 Message-Id: <1550278564-81540-1-git-send-email-yang.shi@linux.alibaba.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since PSI has implemented some kind of measure of memory pressure, the statement about lack of such measure is not true anymore. Cc: Tejun Heo Cc: Johannes Weiner Cc: Jonathan Corbet Signed-off-by: Yang Shi --- Documentation/admin-guide/cgroup-v2.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst index 7bf3f12..9a92013 100644 --- a/Documentation/admin-guide/cgroup-v2.rst +++ b/Documentation/admin-guide/cgroup-v2.rst @@ -1310,8 +1310,7 @@ network to a file can use all available memory but can also operate as performant with a small amount of memory. A measure of memory pressure - how much the workload is being impacted due to lack of memory - is necessary to determine whether a workload needs more -memory; unfortunately, memory pressure monitoring mechanism isn't -implemented yet. +memory. Memory Ownership -- 1.8.3.1