linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Vlastimil Babka <vbabka@suse.cz>, Conor.Dooley@microchip.com
Cc: cl@linux.com, rientjes@google.com, iamjoonsoo.kim@lge.com,
	penberg@kernel.org, 42.hyeyoo@gmail.com, willy@infradead.org,
	roman.gushchin@linux.dev, pasha.tatashin@soleen.com,
	torvalds@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
	rkovhaev@gmail.com, akpm@linux-foundation.org
Subject: Re: Deprecating and removing SLOB
Date: Sat, 12 Nov 2022 10:40:36 +0900	[thread overview]
Message-ID: <ba1d4796-b0ce-1a63-5f9d-c9da7392167d@opensource.wdc.com> (raw)
In-Reply-To: <5a902810-2e72-9021-e189-a1cd2aa6f77f@suse.cz>

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@microchip.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@soleen:~/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



  reply	other threads:[~2022-11-12  1:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 15:55 Vlastimil Babka
2022-11-08 18:18 ` Christophe Leroy
2022-11-08 19:17   ` Andrew Morton
2022-11-08 18:46 ` Roman Gushchin
2022-11-08 20:13   ` Yosry Ahmed
2022-11-09  9:09     ` Vlastimil Babka
2022-11-08 21:44 ` Pasha Tatashin
2022-11-09  9:00   ` Vlastimil Babka
2022-11-09 15:50     ` Aaro Koskinen
2022-11-09 16:45       ` Geert Uytterhoeven
2022-11-09 17:45       ` Mike Rapoport
2022-11-09 21:16       ` Janusz Krzysztofik
2022-11-09 17:57   ` Conor.Dooley
2022-11-09 23:00     ` Damien Le Moal
2022-11-11 10:25       ` Vlastimil Babka
2022-11-12  1:40         ` Damien Le Moal [this message]
2022-11-11 10:33   ` Vlastimil Babka
2022-11-11 20:46     ` Conor Dooley
2022-11-12  1:40       ` Damien Le Moal
2022-11-14  1:55       ` Damien Le Moal
2022-11-14  5:48         ` Damien Le Moal
2022-11-14  9:36           ` Vlastimil Babka
2022-11-14 11:35             ` Damien Le Moal
2022-11-14 14:47               ` Hyeonggon Yoo
2022-11-15  4:24                 ` Damien Le Moal
2022-11-15  4:28                   ` Damien Le Moal
2022-11-16  7:57                     ` Matthew Wilcox
2022-11-16  8:02                       ` Damien Le Moal
2022-11-16 17:51                   ` Vlastimil Babka
2022-11-17  0:22                     ` Damien Le Moal
2022-11-21  4:30                     ` Damien Le Moal
2022-11-21 17:02                       ` Vlastimil Babka
2022-11-14 11:50             ` Hyeonggon Yoo
     [not found]     ` <Y25E9cJbhDAKi1vd@99bb1221be19>
     [not found]       ` <Y26FN02o7jhV87wl@localhost>
2022-11-11 21:11         ` [lkp] [+5395 bytes kernel size regression] [i386-tinyconfig] [b7c8731082] " Vlastimil Babka
2022-11-09 20:56 Paul Cercueil
2022-11-09 21:39 ` Linus Torvalds
2022-11-09 23:48   ` Aaro Koskinen
2022-11-09 23:51     ` Aaro Koskinen
2022-11-10  4:40     ` Theodore Ts'o
2022-11-10  7:31       ` Vlastimil Babka
2022-11-10  7:54         ` Feng Tang
2022-11-10 16:20         ` Matthew Wilcox
2022-11-11  9:37           ` David Laight

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=ba1d4796-b0ce-1a63-5f9d-c9da7392167d@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rkovhaev@gmail.com \
    --cc=roman.gushchin@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    /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