From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id B8013C43219 for ; Wed, 9 Nov 2022 09:01:32 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0E8836B0072; Wed, 9 Nov 2022 04:01:32 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 0980B6B0073; Wed, 9 Nov 2022 04:01:32 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EA21C8E0001; Wed, 9 Nov 2022 04:01:31 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id D7F876B0072 for ; Wed, 9 Nov 2022 04:01:31 -0500 (EST) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id B6454ABE2F for ; Wed, 9 Nov 2022 09:01:31 +0000 (UTC) X-FDA: 80113310382.06.ABCCADC Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf18.hostedemail.com (Postfix) with ESMTP id EDEFB1C002A for ; Wed, 9 Nov 2022 09:01:24 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 79215225AE; Wed, 9 Nov 2022 09:00:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1667984426; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tNgqA/29m6rapVBwLFRJijgTafS7LZvhU0/xyktjM78=; b=kp73N4GrxXnW44EQ0y0a4TB2FDUUhg9bhrveGCZgIn/A1FhubwJpIh1y+hKCy4wXn6co3c 20upJxsrxiH0vy1+PpItIS5Jo6KaTzwXo6xPoQ912M/H7ab2GsZFIjcSfjFjLeN+2kEExt bf66ED4Q+PFwb70volaUmYYdnVvXgi8= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1667984426; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tNgqA/29m6rapVBwLFRJijgTafS7LZvhU0/xyktjM78=; b=jMap4o4c/5oJmcGWZKwu3L1piJFejxuiyCAfS3FvdJDGlPwqXn8NI6LbHqPMV0ko/4ZQLu DUlwcAZMY/Up0yAA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 0E7801331F; Wed, 9 Nov 2022 09:00:26 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Q/7UAipsa2P0ZAAAMHmgww (envelope-from ); Wed, 09 Nov 2022 09:00:26 +0000 Message-ID: <87187c52-ae48-130b-6479-ae1023915bc1@suse.cz> Date: Wed, 9 Nov 2022 10:00:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: Deprecating and removing SLOB Content-Language: en-US To: Pasha Tatashin Cc: Christoph Lameter , David Rientjes , Joonsoo Kim , Pekka Enberg , Hyeonggon Yoo <42.hyeyoo@gmail.com>, Matthew Wilcox , Roman Gushchin , Linus Torvalds , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Catalin Marinas , Rustam Kovhaev , Andrew Morton , Josh Triplett , Arnd Bergmann , Russell King , Alexander Shiyan , Aaro Koskinen , Janusz Krzysztofik , Tony Lindgren , Yoshinori Sato , Rich Felker , Jonas Bonn , Stefan Kristiansson , Stafford Horne , "linux-arm-kernel@lists.infradead.org" , "linux-olinux-omap@vger.kernel.orgmap"@vger.kernel.org, openrisc@lists.librecores.org, linux-riscv@lists.infradead.org, linux-sh@vger.kernel.org References: From: Vlastimil Babka In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1667984490; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=tNgqA/29m6rapVBwLFRJijgTafS7LZvhU0/xyktjM78=; b=U4jLlf4EZGx30+xGXg48Tqn1/xQG5yIx6wHdAjCDRfElGCZhVxRWZwC1B58j4nYdWsaLZj jDMks4KKGIuOOUn6I3+p1e+x1r11cZtg43GRpBt3TLEZKTDr1fmi3oZloIDW5afAbkqCEi H4P3X4lWuzI/pHyJkppval+EIMwG5Rk= ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=kp73N4Gr; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=jMap4o4c; spf=pass (imf18.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1667984490; a=rsa-sha256; cv=none; b=Xlh5WHipOBhloF4c9wD9IG1fGAIIPRCXxrfbnVcYav1R5bEIZGxiQN3/nXbb0DYPCtHxwk nAMW3gAmkU1S94UZFMmSyEPUc1hRLkg1qjIW4xY2cl+ur1vm3eCB5oKOIyKHlk/x5J1W4I hrTyyJp1IcG905snJU/m+hRiwiQf+oU= X-Rspam-User: X-Stat-Signature: xda3mpt5d374ciascndspcb89c5k5bgc X-Rspamd-Queue-Id: EDEFB1C002A Authentication-Results: imf18.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=kp73N4Gr; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=jMap4o4c; spf=pass (imf18.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz; dmarc=none X-Rspamd-Server: rspam02 X-HE-Tag: 1667984484-588416 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 11/8/22 22:44, Pasha Tatashin wrote: > On Tue, Nov 8, 2022 at 10:55 AM Vlastimil Babka wrote: >> >> Hi, >> >> as we all know, we currently have three slab allocators. As we discussed >> at LPC [1], it is my hope that one of these allocators has a future, and >> two of them do not. >> >> The unsurprising reasons include code maintenance burden, other features >> compatible with only a subset of allocators (or more effort spent on the >> features), blocking API improvements (more on that below), and my >> inability to pronounce SLAB and SLUB in a properly distinguishable way, >> without resorting to spelling out the letters. >> >> I think (but may be proven wrong) that SLOB is the easier target of the >> two to be removed, so I'd like to focus on it first. >> >> I believe SLOB can be removed because: >> >> - AFAIK nobody really uses it? It strives for minimal memory footprint >> by putting all objects together, which has its CPU performance costs >> (locking, lack of percpu caching, searching for free space...). I'm not >> aware of any "tiny linux" deployment that opts for this. For example, >> OpenWRT seems to use SLUB and the devices these days have e.g. 128MB >> RAM, not up to 16 MB anymore. I've heard anecdotes that the performance >> SLOB impact is too much for those who tried. Googling for >> "CONFIG_SLOB=y" yielded nothing useful. > > I am all for removing SLOB. > > 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/arm/configs/clps711x_defconfig:CONFIG_SLOB=y > arch/arm/configs/collie_defconfig:CONFIG_SLOB=y > arch/arm/configs/multi_v4t_defconfig:CONFIG_SLOB=y > arch/arm/configs/omap1_defconfig:CONFIG_SLOB=y > arch/arm/configs/pxa_defconfig:CONFIG_SLOB=y > arch/arm/configs/tct_hammer_defconfig:CONFIG_SLOB=y > arch/arm/configs/xcep_defconfig:CONFIG_SLOB=y > arch/openrisc/configs/or1ksim_defconfig:CONFIG_SLOB=y > arch/openrisc/configs/simple_smp_defconfig:CONFIG_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 > arch/sh/configs/rsk7201_defconfig:CONFIG_SLOB=y > arch/sh/configs/rsk7203_defconfig:CONFIG_SLOB=y > arch/sh/configs/se7206_defconfig:CONFIG_SLOB=y > arch/sh/configs/shmin_defconfig:CONFIG_SLOB=y > arch/sh/configs/shx3_defconfig:CONFIG_SLOB=y > kernel/configs/tiny.config:CONFIG_SLOB=y Great point, thanks. Ccing. First mail here: https://lore.kernel.org/all/CA%2BCK2bD-uVGJ0%3D9uc7Lt5zwY%2B2PM2RTcfOhxEd65S7TvTrJULA@mail.gmail.com/ >> >> - Last time we discussed it [2], it seemed SLUB memory requirements can >> be brought very close to SLOB's if needed. Of course it can never have >> as small footprint as SLOB due to separate kmem_caches, but the >> difference is not that significant, unless somebody still tries to use >> Linux on very tiny systems (goes back to the previous point). >> >> Besides the smaller maintenance burden, removing SLOB would allow us to >> do a useful API improvement - the ability to use kfree() for both >> objects allocated by kmalloc() and kmem_cache_alloc(). Currently the >> latter has to be freed by kmem_cache_free(), passing a kmem_cache >> pointer in addition to the object pointer. With SLUB and SLAB, it is >> however possible to use kfree() instead, as the kmalloc caches and the >> rest of kmem_caches are the same and kfree() can lookup the kmem_cache >> from object pointer easily for any of those. XFS has apparently did that >> for years without anyone noticing it's broken on SLOB [3], and >> legitimizing and expanding this would help some use cases beside XFS >> (IIRC Matthew mentioned rcu-based freeing for example). >> >> However for SLOB to support kfree() on all allocations, it would need to >> store object size of allocated objects (which it currently does only for >> kmalloc() objects, prepending a size header to the object), but for >> kmem_cache_alloc() allocations as well. This has been attempted in the >> thread [3] but it bloats the memory usage, especially on architectures >> with large ARCH_KMALLOC_MINALIGN, where the prepended header basically >> has to occupy the whole ARCH_KMALLOC_MINALIGN block to be DMA safe. >> There are ongoing efforts to reduce this minalign, but the memory >> footprint would still increase, going against the purpose of SLOB, so >> again it would be easier if we could just remove it. >> >> So with this thread I'm interested in hearing arguments/use cases for >> keeping SLOB. There might be obviously users of SLOB whom this >> conversation will not reach, so I assume the eventual next step would be >> to deprecate it in a way that those users are notified when building a >> new kernel and can raise their voice then. Is there a good proven way >> how to do that for a config option like this one? >> >> Thanks, >> Vlastimil >> >> [1] https://lpc.events/event/16/contributions/1272/ - slides in the >> slabs.pdf linked there >> [2] >> https://lore.kernel.org/all/20211017135708.GA8442@kvm.asia-northeast3-a.c.our-ratio-313919.internal/#t >> [3] >> https://lore.kernel.org/all/20210930044202.GP2361455@dread.disaster.area/ >> >> >>