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  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:   Tue, 13 Oct 2020 11:52:28 +0800
From:   Muchun Song <>
To:     Cong Wang <>
Cc:     Eric Dumazet <>,
        Eric Dumazet <>,
        Greg KH <>,,
        "Michael S. Tsirkin" <>,
        Jason Wang <>,
        David Miller <>,
        Jakub Kicinski <>,
        Alexey Dobriyan <>,
        Andrew Morton <>,
        Alexey Kuznetsov <>,
        Hideaki YOSHIFUJI <>,
        Steffen Klassert <>,
        Herbert Xu <>,
        Shakeel Butt <>,
        Will Deacon <>, Michal Hocko <>,
        Roman Gushchin <>, Neil Brown <>,
        Mike Rapoport <>,
        Sami Tolvanen <>,
        "Kirill A. Shutemov" <>,
        Feng Tang <>,
        Paolo Abeni <>,
        Willem de Bruijn <>,
        Randy Dunlap <>,
        Florian Westphal <>,,
        Pablo Neira Ayuso <>,
        Dexuan Cui <>,
        Jakub Sitnicki <>,
        Peter Zijlstra <>,
        Christian Brauner <>,
        "Eric W. Biederman" <>,
        Thomas Gleixner <>,,
        Michel Lespinasse <>,
        Jann Horn <>,,, Minchan Kim <>,
        Martin KaFai Lau <>,
        Alexei Starovoitov <>,
        Daniel Borkmann <>,
        Miaohe Lin <>,
        Kees Cook <>,
        LKML <>,,
        Linux Kernel Network Developers <>,
        linux-fsdevel <>,
        linux-mm <>
Subject: Re: [External] Re: [PATCH] mm: proc: add Sock to /proc/meminfo

On Tue, Oct 13, 2020 at 6:12 AM Cong Wang <> wrote:
> On Mon, Oct 12, 2020 at 2:53 AM Muchun Song <> wrote:
> > We are not complaining about TCP using too much memory, but how do
> > we know that TCP uses a lot of memory. When I firstly face this problem,
> > I do not know who uses the 25GB memory and it is not shown in the /proc/meminfo.
> > If we can know the amount memory of the socket buffer via /proc/meminfo, we
> > may not need to spend a lot of time troubleshooting this problem. Not everyone
> > knows that a lot of memory may be used here. But I believe many people
> > should know /proc/meminfo to confirm memory users.
> Well, I'd bet networking people know `ss -m` better than /proc/meminfo,

I agree with you. But if someone(not networking people) faces the same
problem. He may suspect that there is a memory leak or think that a certain
driver allocates memory but has no statistics. He only saw the memory
disappeared via /proc/meminfo.

> generally speaking.
> The practice here is that if you want some networking-specific counters,
> add it to where networking people know better, that is, `ss -m` or /proc/net/...
> Or maybe the problem you described is not specific to networking at all,
> there must be some other places where pages are allocated but not charged.

Yeah, it is not charged. The allocation path is as follows. This allocation
consumes 25GB memory on our server. And it belongs to the network core.



> If so, adding a general mm counter in /proc/meminfo makes sense, but
> it won't be specific to networking.
> Thanks.


Powered by blists - more mailing lists