[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2101270907260.673600@www.lameter.com>
Date: Wed, 27 Jan 2021 09:10:14 +0000 (UTC)
From: Christoph Lameter <cl@...ux.com>
To: Will Deacon <will@...nel.org>
cc: Vlastimil Babka <vbabka@...e.cz>,
Vincent Guittot <vincent.guittot@...aro.org>,
Bharata B Rao <bharata@...ux.ibm.com>,
linux-kernel <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>, guro@...com,
Shakeel Butt <shakeelb@...gle.com>,
Johannes Weiner <hannes@...xchg.org>,
aneesh.kumar@...ux.ibm.com, Jann Horn <jannh@...gle.com>,
Michal Hocko <mhocko@...nel.org>,
Catalin Marinas <Catalin.Marinas@....com>
Subject: Re: [RFC PATCH v0] mm/slub: Let number of online CPUs determine the
slub page order
On Tue, 26 Jan 2021, Will Deacon wrote:
> > Hm, but booting the secondaries is just a software (kernel) action? They are
> > already physically there, so it seems to me as if the cpu_present_mask is not
> > populated correctly on arm64, and it's just a mirror of cpu_online_mask?
>
> I think the present_mask retains CPUs if they are hotplugged off, whereas
> the online mask does not. We can't really do any better on arm64, as there's
> no way of telling that a CPU is present until we've seen it.
The order of each page in a kmem cache --and therefore also the number
of objects in a slab page-- can be different because that information is
stored in the page struct.
Therefore it is possible to retune the order while the cache is in operaton.
This means you can run an initcall after all cpus have been brought up to
set the order and number of objects in a slab page differently.
The older slab pages will continue to exist with the old orders until they
are freed.
Powered by blists - more mailing lists