[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <043c49e4-2665-318a-5acb-7081768bc1f3@suse.cz>
Date: Wed, 13 Dec 2023 12:23:26 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: "Song, Xiongwei" <Xiongwei.Song@...driver.com>,
"sxwjean@...com" <sxwjean@...com>,
"42.hyeyoo@...il.com" <42.hyeyoo@...il.com>,
"cl@...ux.com" <cl@...ux.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Cc: "penberg@...nel.org" <penberg@...nel.org>,
"rientjes@...gle.com" <rientjes@...gle.com>,
"iamjoonsoo.kim@....com" <iamjoonsoo.kim@....com>,
"roman.gushchin@...ux.dev" <roman.gushchin@...ux.dev>,
"corbet@....net" <corbet@....net>,
"keescook@...omium.org" <keescook@...omium.org>,
"arnd@...db.de" <arnd@...db.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 4/4] mm/slub: correct the default value of
slub_min_objects in doc
On 12/9/23 14:59, Song, Xiongwei wrote:
> I didn't change description as you mentioned because slab_min_objects doesn't
> save the calculated value based on the number of processors, but the local
> variables min_objects doesn't.
Hm I think that's less helpful. The user/admin who will read the doc doesn't
care about implementation details such as value of a variable, but what's
the actual observable default behavior, and that is still the automatic
scaling, right?
> Regards,
> Xiongwei
Powered by blists - more mailing lists