linux-kernel - Re: [RFC 0/6] mm: improve page allocator scalability via splitting zones

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: <ZGIUEqhSydAdvRFN@dhcp22.suse.cz>
Date:   Mon, 15 May 2023 13:14:26 +0200
From:   Michal Hocko <mhocko@...e.com>
To:     "Huang, Ying" <ying.huang@...el.com>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        Arjan Van De Ven <arjan@...ux.intel.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Vlastimil Babka <vbabka@...e.cz>,
        David Hildenbrand <david@...hat.com>,
        Johannes Weiner <jweiner@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Pavel Tatashin <pasha.tatashin@...een.com>,
        Matthew Wilcox <willy@...radead.org>
Subject: Re: [RFC 0/6] mm: improve page allocator scalability via splitting
 zones

On Fri 12-05-23 10:55:21, Huang, Ying wrote:
> Hi, Michal,
> 
> Thanks for comments!
> 
> Michal Hocko <mhocko@...e.com> writes:
> 
> > On Thu 11-05-23 14:56:01, Huang Ying wrote:
> >> The patchset is based on upstream v6.3.
> >> 
> >> More and more cores are put in one physical CPU (usually one NUMA node
> >> too).  In 2023, one high-end server CPU has 56, 64, or more cores.
> >> Even more cores per physical CPU are planned for future CPUs.  While
> >> all cores in one physical CPU will contend for the page allocation on
> >> one zone in most cases.  This causes heavy zone lock contention in
> >> some workloads.  And the situation will become worse and worse in the
> >> future.
> >> 
> >> For example, on an 2-socket Intel server machine with 224 logical
> >> CPUs, if the kernel is built with `make -j224`, the zone lock
> >> contention cycles% can reach up to about 12.7%.
> >> 
> >> To improve the scalability of the page allocation, in this series, we
> >> will create one zone instance for each about 256 GB memory of a zone
> >> type generally.  That is, one large zone type will be split into
> >> multiple zone instances.  Then, different logical CPUs will prefer
> >> different zone instances based on the logical CPU No.  So the total
> >> number of logical CPUs contend on one zone will be reduced.  Thus the
> >> scalability is improved.
> >
> > It is not really clear to me why you need a new zone for all this rather
> > than partition free lists internally within the zone? Essentially to
> > increase the current two level system to 3: per cpu caches, per cpu
> > arenas and global fallback.
> 
> Sorry, I didn't get your idea here.  What is per cpu arenas?  What's the
> difference between it and per cpu caches (PCP)?

Sorry, I didn't give this much thought than the above. Essentially, we
have 2 level system right now. Pcp caches should reduce the contention
on the per cpu level and that should work reasonably well, if you manage
to align batch sizes to the workload AFAIK. If this is not sufficient
then why to add the full zone rather than to add another level that
caches across a larger than a cpu unit. Maybe a core?

This might be a wrong way around going for this but there is not much
performance analysis about the source of the lock contention so I am
mostly guessing.

> > I am also missing some information why pcp caches tunning is not
> > sufficient.
> 
> PCP does improve the page allocation scalability greatly!  But it
> doesn't help much for workloads that allocating pages on one CPU and
> free them in different CPUs.  PCP tuning can improve the page allocation
> scalability for a workload greatly.  But it's not trivial to find the
> best tuning parameters for various workloads and workload run time
> statuses (workloads may have different loads and memory requirements at
> different time).  And we may run different workloads on different
> logical CPUs of the system.  This also makes it hard to find the best
> PCP tuning globally.

Yes this makes sense. Does that mean that the global pcp tuning is not
keeping up and we need to be able to do more auto-tuning on local bases
rather than global?

> It would be better to find a solution to improve
> the page allocation scalability out of box or automatically.  Do you
> agree?

Yes. 

-- 
Michal Hocko
SUSE Labs