linux-kernel - Re: [PATCH v4 00/17] Optimize list lru memory consumption

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: <YbyM17OMHlEmLfhH@casper.infradead.org>
Date:   Fri, 17 Dec 2021 13:12:55 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     xiaoqiang zhao <zhaoxiaoqiang007@...il.com>
Cc:     Muchun Song <songmuchun@...edance.com>, akpm@...ux-foundation.org,
        hannes@...xchg.org, mhocko@...nel.org, vdavydov.dev@...il.com,
        shakeelb@...gle.com, guro@...com, shy828301@...il.com,
        alexs@...nel.org, richard.weiyang@...il.com, david@...morbit.com,
        trond.myklebust@...merspace.com, anna.schumaker@...app.com,
        jaegeuk@...nel.org, chao@...nel.org, kari.argillander@...il.com,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, linux-nfs@...r.kernel.org,
        zhengqi.arch@...edance.com, duanxiongchun@...edance.com,
        fam.zheng@...edance.com, smuchun@...il.com
Subject: Re: [PATCH v4 00/17] Optimize list lru memory consumption

On Fri, Dec 17, 2021 at 06:05:00PM +0800, xiaoqiang zhao wrote:
> 
> 
> 在 2021/12/14 0:53, Muchun Song 写道:
> > This series is based on Linux 5.16-rc3.
> > 
> > In our server, we found a suspected memory leak problem. The kmalloc-32
> > consumes more than 6GB of memory. Other kmem_caches consume less than 2GB
> > memory.
> > 
> > After our in-depth analysis, the memory consumption of kmalloc-32 slab
> > cache is the cause of list_lru_one allocation.
> 
> IIUC, you mean: "the memory consumption of kmalloc-32 slab cache is
> caused by list_lru_one allocation"
> 

Please trim the unnecessary parts.  You quoted almost 200 extra lines
after this that I (and everybody else reading) have to look through
to see if you said anything else.