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  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]
Date:   Fri, 24 Nov 2017 13:30:25 +0000
From:   Vaneet Narang <>
To:     Michal Hocko <>
CC:     Dmitry Vyukov <>,
        Maninder Singh <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        AMIT SAHRAWAT <>,
        PANKAJ MISHRA <>,
        Lalit Mohan Tripathi <>,
        "" <>,
        "" <>,
        kasan-dev <>
Subject: RE: Re: Re: [PATCH 1/1] stackdepot: interface to check entries and
 size of stackdepot.

Hi Michal,

>> We have been getting similar kind of such entries and eventually
>> stackdepot reaches Max Cap. So we found this interface useful in debugging
>> stackdepot issue so shared in community.
>Then use it for internal debugging and provide a code which would scale
>better on smaller systems. We do not need this in the kernel IMHO. We do
>not merge all the debugging patches we use for internal development.
Not just debugging but this information can also be used to profile and tune stack depot. 
Getting count of stack entries would help in deciding hash table size and 
page order used by stackdepot. 

For less entries, bigger hash table and higher page order slabs might not be required as 
maintained by stackdepot. As i already mentioned smaller size hashtable can be choosen and 
similarly lower order  pages can be used for slabs.

If you think its useful, we can share scalable patch to configure below two values based on 
number of stack entries dynamically.


Vaneet Narang

Powered by blists - more mailing lists