linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Song, Xiongwei" <Xiongwei.Song@windriver.com>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>, "sxwjean@me.com" <sxwjean@me.com>
Cc: "cl@linux.com" <cl@linux.com>,
	"penberg@kernel.org" <penberg@kernel.org>,
	"rientjes@google.com" <rientjes@google.com>,
	"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
	"vbabka@suse.cz" <vbabka@suse.cz>,
	"roman.gushchin@linux.dev" <roman.gushchin@linux.dev>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/4] Documentation: kernel-parameters: remove slab_max_order
Date: Wed, 22 Nov 2023 05:19:32 +0000	[thread overview]
Message-ID: <CO1PR11MB5185785954F94B92A29567C7ECBAA@CO1PR11MB5185.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAB=+i9SYr8vMVzRhj2zpK3zX8Qj2pf8yrvVC0_g=cqbOa8n0uA@mail.gmail.com>



> -----Original Message-----
> From: owner-linux-mm@kvack.org <owner-linux-mm@kvack.org> On Behalf Of Hyeonggon
> Yoo
> Sent: Tuesday, November 21, 2023 4:30 PM
> To: sxwjean@me.com
> Cc: cl@linux.com; penberg@kernel.org; rientjes@google.com; iamjoonsoo.kim@lge.com;
> vbabka@suse.cz; roman.gushchin@linux.dev; corbet@lwn.net; linux-mm@kvack.org; linux-
> doc@vger.kernel.org; linux-kernel@vger.kernel.org
> 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@me.com> wrote:
> >
> > From: Xiongwei Song <xiongwei.song@windriver.com>
> >
> > Since slab allocator has already been removed. There is no users about
> > it, so remove it.
> >
> > Signed-off-by: Xiongwei Song <xiongwei.song@windriver.com>
> > ---
> >  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


  reply	other threads:[~2023-11-22  5:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  9:12 [PATCH 0/4] supplement of slab removal sxwjean
2023-11-20  9:12 ` [PATCH 1/4] Documentation: kernel-parameters: remove slab_max_order sxwjean
2023-11-21  8:30   ` Hyeonggon Yoo
2023-11-22  5:19     ` Song, Xiongwei [this message]
2023-11-20  9:12 ` [PATCH 2/4] mm/slab: remove slab_nomrege and slab_merge sxwjean
2023-11-21  8:44   ` Hyeonggon Yoo
2023-11-22  5:27     ` Song, Xiongwei
2023-11-22  5:59       ` Hyeonggon Yoo
2023-11-20  9:12 ` [PATCH 3/4] mm/slab: make calculate_alignment() public sxwjean
2023-11-20  9:12 ` [PATCH 4/4] mm/slab: move slab merge from slab_common.c to slub.c sxwjean
2023-11-21  8:54   ` Hyeonggon Yoo
2023-11-21 10:03     ` Vlastimil Babka
2023-11-22  5:29       ` Song, Xiongwei
2023-11-21  9:01   ` Hyeonggon Yoo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO1PR11MB5185785954F94B92A29567C7ECBAA@CO1PR11MB5185.namprd11.prod.outlook.com \
    --to=xiongwei.song@windriver.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=sxwjean@me.com \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox