[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <73359971-25bc-8ce9-3dd1-b3124c18628b@suse.cz>
Date: Wed, 13 Dec 2023 12:10:02 +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: [RFC PATCH v2 2/3] mm/slub: unify all sl[au]b parameters with
"slab_$param"
On 12/9/23 02:02, Song, Xiongwei wrote:
>
>
>> -----Original Message-----
>> From: Vlastimil Babka <vbabka@...e.cz>
>> Sent: Thursday, December 7, 2023 12:15 AM
>> To: sxwjean@...com; 42.hyeyoo@...il.com; cl@...ux.com; linux-mm@...ck.org
>> Cc: penberg@...nel.org; rientjes@...gle.com; iamjoonsoo.kim@....com;
>> roman.gushchin@...ux.dev; corbet@....net; keescook@...omium.org; arnd@...db.de;
>> akpm@...ux-foundation.org; gregkh@...uxfoundation.org; linux-doc@...r.kernel.org; linux-
>> kernel@...r.kernel.org; Song, Xiongwei <Xiongwei.Song@...driver.com>
>> Subject: Re: [RFC PATCH v2 2/3] mm/slub: unify all sl[au]b parameters with "slab_$param"
>>
>>
>> On 12/3/23 01:15, sxwjean@...com wrote:
>> > From: Xiongwei Song <xiongwei.song@...driver.com>
>> >
>> > Since the SLAB allocator has been removed, so we need to clean up the
>>
>> "we can clean up", as we don't really "need"
>>
>> > sl[au]b_$params. However, the "slab/SLAB" terms should be keep for
>> > long-term rather than "slub/SLUB". Hence, we should use "slab_$param"
>>
>> I'd phrase it: With only one slab allocator left, it's better to use the
>> generic "slab" term instead of "slub" which is an implementation detail.
>> Hence ...
>>
>> > as the primary prefix, which is pointed out by Vlastimil Babka. For more
>> > information please see [1].
>> >
>> > This patch is changing the following slab parameters
>> > - slub_max_order
>> > - slub_min_order
>> > - slub_min_objects
>> > - slub_debug
>> > to
>> > - slab_max_order
>> > - slab_min_order
>> > - slab_min_objects
>> > - slab_debug
>> > as the primary slab parameters in
>> > Documentation/admin-guide/kernel-parameters.txt and source, and rename all
>> > setup functions of them too. Meanwhile, "slub_$params" can also be passed
>>
>> Not sure about renaming the code at this point, I would just rename the
>> user-visible parameters and their documentation and any comment that refers
>> to the parameters. Functions and variables can come later as part of wider
>> slub/slab change if we decide to do so?
>
> I think we can rename these global variables:
> slub_max_order,
> slub_min_order,
> slub_min_objects,
> slub_debug
> , which are used to save values that are from parameters. Because some comments
> are referring to parameters, the others are referring to these global variables, which
> looks inconsistent, e.g. slub_debug/slab_debug. Is it acceptable to make them
> consistent?
Yeah, as an additional patch.
Thanks.
Powered by blists - more mailing lists