[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba1d4796-b0ce-1a63-5f9d-c9da7392167d@opensource.wdc.com>
Date: Sat, 12 Nov 2022 10:40:36 +0900
From: Damien Le Moal <damien.lemoal@...nsource.wdc.com>
To: Vlastimil Babka <vbabka@...e.cz>, Conor.Dooley@...rochip.com
Cc: cl@...ux.com, rientjes@...gle.com, iamjoonsoo.kim@....com,
penberg@...nel.org, 42.hyeyoo@...il.com, willy@...radead.org,
roman.gushchin@...ux.dev, pasha.tatashin@...een.com,
torvalds@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, catalin.marinas@....com,
rkovhaev@...il.com, akpm@...ux-foundation.org
Subject: Re: Deprecating and removing SLOB
On 11/11/22 19:25, Vlastimil Babka wrote:
> On 11/10/22 00:00, Damien Le Moal wrote:
>> On 11/10/22 02:57, Conor.Dooley@...rochip.com wrote:
>>> +CC Damien
>>>
>>>> There are some devices with configs where SLOB is enabled by default.
>>>> Perhaps, the owners/maintainers of those devices/configs should be
>>>> included into this thread:
>>>>
>>>> tatashin@...een:~/x/linux$ git grep SLOB=y
>>>
>>>> arch/riscv/configs/nommu_k210_defconfig:CONFIG_SLOB=y
>>>> arch/riscv/configs/nommu_k210_sdcard_defconfig:CONFIG_SLOB=y
>>>> arch/riscv/configs/nommu_virt_defconfig:CONFIG_SLOB=y
>>>
>>> Saw you were not added to the CC Damien & I know you don't want your
>>> baby broken!
>>
>> :)
>>
>> I set SLOB=y for the K210 as the config help mentions it is a bit more
>> efficient in low memory cases. I did run a few times with SLAB and it
>> was OK, so removing slob should not be a problem. Can check again.
>
> Thanks, but please check with SLUB, not SLAB, if possible.
> Disable SLUB_CPU_PARTIAL (default y on SMP) if you want to minimize the
> memory usage.
Thanks for the hint. Will try that.
--
Damien Le Moal
Western Digital Research
Powered by blists - more mailing lists