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: <a324af3f-f5c4-8c26-400e-ca3a590db37d@alibaba-inc.com>
Date:   Wed, 18 Oct 2017 06:20:09 +0800
From:   "Yang Shi" <yang.s@...baba-inc.com>
To:     David Rientjes <rientjes@...gle.com>
Cc:     Michal Hocko <mhocko@...nel.org>, cl@...ux.com, penberg@...nel.org,
        iamjoonsoo.kim@....com, akpm@...ux-foundation.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when
 unreclaimable slabs > user memory



On 10/17/17 2:50 PM, David Rientjes wrote:
> On Wed, 18 Oct 2017, Yang Shi wrote:
> 
>>>>> Please simply dump statistics for all slab caches where the memory
>>>>> footprint is greater than 5% of system memory.
>>>>
>>>> Unconditionally? User controlable?
>>>
>>> Unconditionally, it's a single line of output per slab cache and there
>>> can't be that many of them if each is using >5% of memory.
>>
>> So,you mean just dump the single slab cache if its size > 5% of system memory
>> instead of all slab caches?
>>
> 
> Yes, this should catch occurrences of "huge unreclaimable slabs", right?

Yes, it sounds so. Although single "huge" unreclaimable slab might not 
result in excessive slabs use in a whole, but this would help to filter 
out "small" unreclaimable slab.

Yang

> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ