From: "Song, Xiongwei" <Xiongwei.Song@windriver.com>
To: Kees Cook <keescook@chromium.org>, "sxwjean@me.com" <sxwjean@me.com>
Cc: "vbabka@suse.cz" <vbabka@suse.cz>,
"42.hyeyoo@gmail.com" <42.hyeyoo@gmail.com>,
"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>,
"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 3/3] mm/slub: correct the default value of slub_min_objects in doc
Date: Sat, 2 Dec 2023 04:22:06 +0000 [thread overview]
Message-ID: <PH0PR11MB5192C83167C9A7C033B1DCA5EC80A@PH0PR11MB5192.namprd11.prod.outlook.com> (raw)
In-Reply-To: <202312010948.63ACCAAE@keescook>
> -----Original Message-----
> From: Kees Cook <keescook@chromium.org>
> Sent: Saturday, December 2, 2023 1:50 AM
> To: sxwjean@me.com
> Cc: vbabka@suse.cz; 42.hyeyoo@gmail.com; cl@linux.com; linux-mm@kvack.org;
> penberg@kernel.org; rientjes@google.com; iamjoonsoo.kim@lge.com;
> roman.gushchin@linux.dev; corbet@lwn.net; 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 3/3] mm/slub: correct the default value of slub_min_objects in doc
>
> 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 Fri, Dec 01, 2023 at 11:15:05AM +0800, sxwjean@me.com wrote:
> > From: Xiongwei Song <xiongwei.song@windriver.com>
> >
> > There is no a value assigned to slub_min_objects by default, it awlays
> ^^^^^^
> > is 0 that is intailized by compiler if no assigned value by command line.
> ^^^^^^^^^^
> > min_objects is calculated based on proccessor numbers in
> ^^^^^^^^^^
> > calculate_order(). For more details, see commit 9b2cd506e5f2 ("slub:
> > Calculate min_objects based on number of processors.")
>
> nit: multiple spelling mistakes here. Please double-check commit logs
> with a spell checker. :)
Sorry for those mistakes. Will update.
Regards,
Xiongwei
>
> >
> > Signed-off-by: Xiongwei Song <xiongwei.song@windriver.com>
> > ---
> > 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))
>
> But otherwise, yes, this change matches what the code does.
>
> -Kees
>
> --
> Kees Cook
prev parent reply other threads:[~2023-12-02 4:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 3:15 [PATCH 0/3] supplyment of slab allocator removal sxwjean
2023-12-01 3:15 ` [PATCH 1/3] Documentation: kernel-parameters: remove noaliencache sxwjean
2023-12-01 17:45 ` Kees Cook
2023-12-01 3:15 ` [RFC PATCH 2/3] mm/slub: unify all sl[au]b parameters with "slab_$param" sxwjean
2023-12-01 17:47 ` Kees Cook
2023-12-02 4:23 ` Song, Xiongwei
2023-12-02 18:12 ` Vlastimil Babka
2023-12-02 21:30 ` Kees Cook
2023-12-06 14:59 ` Vlastimil Babka
2023-12-01 3:15 ` [PATCH 3/3] mm/slub: correct the default value of slub_min_objects in doc sxwjean
2023-12-01 17:50 ` Kees Cook
2023-12-02 4:22 ` Song, Xiongwei [this message]
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=PH0PR11MB5192C83167C9A7C033B1DCA5EC80A@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