linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Song, Xiongwei" <Xiongwei.Song@windriver.com>
To: Vlastimil Babka <vbabka@suse.cz>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	"sxwjean@me.com" <sxwjean@me.com>
Cc: "cl@linux.com" <cl@linux.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"penberg@kernel.org" <penberg@kernel.org>,
	"rientjes@google.com" <rientjes@google.com>,
	"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
	"roman.gushchin@linux.dev" <roman.gushchin@linux.dev>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 3/3] mm/slub: correct the default value of slub_min_objects in doc
Date: Fri, 8 Dec 2023 23:17:12 +0000	[thread overview]
Message-ID: <PH0PR11MB51922EE600CA6EA6660EBE59EC8AA@PH0PR11MB5192.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9649f3fc-1802-6a0b-e492-d1ef6965d442@suse.cz>



> -----Original Message-----
> From: Vlastimil Babka <vbabka@suse.cz>
> Sent: Thursday, December 7, 2023 12:34 AM
> To: Hyeonggon Yoo <42.hyeyoo@gmail.com>; sxwjean@me.com
> Cc: cl@linux.com; linux-mm@kvack.org; penberg@kernel.org; rientjes@google.com;
> iamjoonsoo.kim@lge.com; roman.gushchin@linux.dev; corbet@lwn.net;
> keescook@chromium.org; arnd@arndb.de; akpm@linux-foundation.org;
> gregkh@linuxfoundation.org; linux-doc@vger.kernel.org; linux-kernel@vger.kernel.org; Song,
> Xiongwei <Xiongwei.Song@windriver.com>
> Subject: Re: [PATCH v2 3/3] mm/slub: correct the default value of slub_min_objects in doc
> 
> On 12/5/23 01:53, Hyeonggon Yoo wrote:
> > On Sun, Dec 3, 2023 at 9:16 AM <sxwjean@me.com> wrote:
> >>
> >> From: Xiongwei Song <xiongwei.song@windriver.com>
> >>
> >> There is no a value assigned to slub_min_objects by default, it always
> >> is 0 that is initialized by compiler if no assigned value by command line.
> >> min_objects is calculated based on processor numbers in calculate_order().
> >> For more details, see commit 9b2cd506e5f2 ("slub: Calculate min_objects
> >> based on number of processors.")
> >>
> >> Signed-off-by: Xiongwei Song <xiongwei.song@windriver.com>
> >
> > While slub_min_objects equals zero by default, 'min_objects' overrides it to
> > 4 * (fls(nr_cpus) + 1) when not set. so when slub_min_objects is not
> > set, it would be
> > equal to or higher than 4. I'm not sure this level of implementation
> > detail is worth documenting.
> 
> We could say e.g. "(default: automaticaly scaled by number of cpus)"

Ah, looks better.

> 
> > Also, I think patch 2 should update Documentation/mm/slub.rst too.
> > (slub_$param -> slab_param)
> 
> I'd do it as separate patch, not part of patch 2.

Will do. 

Thanks

> 
> >> ---
> >>  Documentation/mm/slub.rst | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/Documentation/mm/slub.rst b/Documentation/mm/slub.rst
> >> index be75971532f5..1f4399581449 100644
> >> --- a/Documentation/mm/slub.rst
> >> +++ b/Documentation/mm/slub.rst
> >> @@ -150,7 +150,7 @@ list_lock once in a while to deal with partial slabs. That overhead
> is
> >>  governed by the order of the allocation for each slab. The allocations
> >>  can be influenced by kernel parameters:
> >>
> >> -.. slub_min_objects=x          (default 4)
> >> +.. slub_min_objects=x          (default 0)
> >>  .. slub_min_order=x            (default 0)
> >>  .. slub_max_order=x            (default 3 (PAGE_ALLOC_COSTLY_ORDER))
> >>
> >> --
> >> 2.34.1
> >>


  reply	other threads:[~2023-12-08 23:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03  0:14 [PATCH v2 0/3] supplement of slab allocator removal sxwjean
2023-12-03  0:14 ` [PATCH v2 1/3] Documentation: kernel-parameters: remove noaliencache sxwjean
2023-12-06 15:35   ` Vlastimil Babka
2023-12-03  0:15 ` [RFC PATCH v2 2/3] mm/slub: unify all sl[au]b parameters with "slab_$param" sxwjean
2023-12-06 16:14   ` Vlastimil Babka
2023-12-08  1:58     ` Song, Xiongwei
2023-12-09  1:02     ` Song, Xiongwei
2023-12-13 11:10       ` Vlastimil Babka
2023-12-03  0:15 ` [PATCH v2 3/3] mm/slub: correct the default value of slub_min_objects in doc sxwjean
2023-12-05  0:53   ` Hyeonggon Yoo
2023-12-05 14:10     ` Song, Xiongwei
2023-12-06  0:22       ` Hyeonggon Yoo
2023-12-06 14:33         ` Song, Xiongwei
2023-12-06 16:33     ` Vlastimil Babka
2023-12-08 23:17       ` Song, Xiongwei [this message]
2023-12-06 16:13 ` [PATCH v2 0/3] supplement of slab allocator removal Vlastimil Babka
2023-12-08  2:03   ` Song, Xiongwei

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=PH0PR11MB51922EE600CA6EA6660EBE59EC8AA@PH0PR11MB5192.namprd11.prod.outlook.com \
    --to=xiongwei.song@windriver.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=keescook@chromium.org \
    --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