linux-kernel - Re: [PATCH] doc: cgroup: correct the wrong information about measure of memory pressure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <79dc6298-a062-51e0-64d0-9696dc602767@linux.alibaba.com>
Date:   Tue, 19 Feb 2019 08:47:02 -0800
From:   Yang Shi <yang.shi@...ux.alibaba.com>
To:     Tejun Heo <tj@...nel.org>
Cc:     hannes@...xchg.org, corbet@....net, cgroups@...r.kernel.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] doc: cgroup: correct the wrong information about measure
 of memory pressure



On 2/18/19 1:05 PM, Tejun Heo wrote:
> On Sat, Feb 16, 2019 at 08:56:04AM +0800, Yang Shi wrote:
>> 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 <tj@...nel.org>
>> Cc: Johannes Weiner <hannes@...xchg.org>
>> Cc: Jonathan Corbet <corbet@....net>
>> Signed-off-by: Yang Shi <yang.shi@...ux.alibaba.com>
>> ---
>>   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.
> Maybe refer to PSI?

I thought so too, but the above "memory.pressure" has already referred 
to PSI. So, I was not sure if we should duplicate PSI information.

Thanks,
Yang

>
> Thanks.
>