RE: [PATCH 1/4] Documentation: kernel-parameters: remove slab_max_order

From: Song, Xiongwei
Date: Wed Nov 22 2023 - 00:20:30 EST




> -----Original Message-----
> From: owner-linux-mm@xxxxxxxxx <owner-linux-mm@xxxxxxxxx> On Behalf Of Hyeonggon
> Yoo
> Sent: Tuesday, November 21, 2023 4:30 PM
> To: sxwjean@xxxxxx
> Cc: cl@xxxxxxxxx; penberg@xxxxxxxxxx; rientjes@xxxxxxxxxx; iamjoonsoo.kim@xxxxxxx;
> vbabka@xxxxxxx; roman.gushchin@xxxxxxxxx; corbet@xxxxxxx; linux-mm@xxxxxxxxx; linux-
> doc@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH 1/4] Documentation: kernel-parameters: remove slab_max_order
>
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the
> content is safe.
>
> On Mon, Nov 20, 2023 at 6:12 PM <sxwjean@xxxxxx> wrote:
> >
> > From: Xiongwei Song <xiongwei.song@xxxxxxxxxxxxx>
> >
> > Since slab allocator has already been removed. There is no users about
> > it, so remove it.
> >
> > Signed-off-by: Xiongwei Song <xiongwei.song@xxxxxxxxxxxxx>
> > ---
> > Documentation/admin-guide/kernel-parameters.txt | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-
> guide/kernel-parameters.txt
> > index 65731b060e3f..c7709a11f8ce 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -5887,12 +5887,6 @@
> > own.
> > For more information see Documentation/mm/slub.rst.
> >
> > - slab_max_order= [MM, SLAB]
> > - Determines the maximum allowed order for slabs.
> > - A high setting may cause OOMs due to memory
> > - fragmentation. Defaults to 1 for systems with
> > - more than 32MB of RAM, 0 otherwise.
> > -
>
> Good catch!
>
> By the way I think noaliencache can be removed too in this patch together:

Thanks Hyeonggon. Will do that.

Regards,
Xiongwei

> > noaliencache [MM, NUMA, SLAB] Disables the allocation of alien
> > caches in the slab allocator. Saves per-node memory,
> > but will impact performance.
>
> Thanks,
> Hyeonggon