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:   Wed, 23 Sep 2020 10:35:29 +0800
From:   Chunxin Zang <>
To:     Chris Down <>
Cc:     Michal Hocko <>, Yafang Shao <>,
        Johannes Weiner <>,
        Vladimir Davydov <>,
        Andrew Morton <>,
        Tejun Heo <>,,
        Jonathan Corbet <>,
        Alexei Starovoitov <>,
        Daniel Borkmann <>,,
        Song Liu <>, Yonghong Song <>,,,,
        Cgroups <>,,
        Linux MM <>,
        LKML <>,
        netdev <>,
Subject: Re: [External] Re: [PATCH] mm/memcontrol: Add the drop_cache
 interface for cgroup v2

On Tue, Sep 22, 2020 at 8:43 PM Chris Down <> wrote:
> Chunxin Zang writes:
> >Please forgive me for not being able to understand why setting
> >memory.low for Type_A can solve the problem.
> >In my scene, Type_A is the most important, so I will set 100G to memory.low.
> >But 'memory.low' only takes effect passively when the kernel is
> >reclaiming memory. It means that reclaim Type_B's memory only when
> >Type_A  in alloc memory slow path. This will affect Type_A's
> >performance.
> >We want to reclaim Type_B's memory in advance when A is expected to be busy.
> That's what kswapd reclaim is for, so this distinction is meaningless without
> measurements :-)

Thanks for these suggestions, I will give it a try.

Best wishes

Powered by blists - more mailing lists