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 C270DC36010 for ; Tue, 1 Apr 2025 23:16:38 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6F854280002; Tue, 1 Apr 2025 19:16:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 6A65B280001; Tue, 1 Apr 2025 19:16:37 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 595B3280002; Tue, 1 Apr 2025 19:16:37 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 3C29F280001 for ; Tue, 1 Apr 2025 19:16:37 -0400 (EDT) Received: from smtpin22.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 9AF38B90A6 for ; Tue, 1 Apr 2025 23:16:37 +0000 (UTC) X-FDA: 83287036434.22.1A37C14 Received: from out-171.mta1.migadu.com (out-171.mta1.migadu.com [95.215.58.171]) by imf12.hostedemail.com (Postfix) with ESMTP id 9E08740009 for ; Tue, 1 Apr 2025 23:16:35 +0000 (UTC) Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=lrccqYEj; spf=pass (imf12.hostedemail.com: domain of shakeel.butt@linux.dev designates 95.215.58.171 as permitted sender) smtp.mailfrom=shakeel.butt@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1743549396; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=hdYFel7Qn8dZFBBGFQF9DcgBfGpsPkEhqKjG8L5kMI4=; b=kzPRkYjvRrdBtgfHu1fW6M+BXBHSOL/x+zyEHGL8tWI9+U1WDp7zhoSjUIUzKhnz/z+3Xh 7DuiGyxX3PXmG9CyCpX2huoyCi7taMoxmPy3rCbOpd2nGXOySYuqhRfGrc0ZT3aKpopyvh ciJQedjMO7ber5DoSXJ8Kmvx8ruom5M= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=lrccqYEj; spf=pass (imf12.hostedemail.com: domain of shakeel.butt@linux.dev designates 95.215.58.171 as permitted sender) smtp.mailfrom=shakeel.butt@linux.dev; dmarc=pass (policy=none) header.from=linux.dev ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1743549396; a=rsa-sha256; cv=none; b=OSrX6EE3qXFFJtsGjcKH97ytS0Q2Hg3u2TWVr+NWxPDpAH318RV1xBz1zjFy/rA9AOnF+g JDY4Oell/BvXbdJaMa+/K2mvRoFzNsHbWPxpGnJdEYRrIZxv5GoYavMf13JcV+Ty06AE3f dHO2gdNASKe0sDaybYTQP1khNG2iAR8= Date: Tue, 1 Apr 2025 16:16:26 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1743549393; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hdYFel7Qn8dZFBBGFQF9DcgBfGpsPkEhqKjG8L5kMI4=; b=lrccqYEjr75XGIU0QuMjIahkzeh3niO+D1j5rUYTqsGNAMYkPKNJ3mWPRYARqI2C+VwmF1 AZgonJqNP8PfgNkqDlpqITiXpvqjcrAbyc7tNOL7bqgyFFzvmbeXIpi6352DeUUcblRVX1 +2AdEqGOTfyQBdYAzN+TwyqfR3GP9lM= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Shakeel Butt To: Vitaly Wool Cc: linux-mm@kvack.org, akpm@linux-foundation.org, Igor Belousov Subject: Re: [PATCH] mm: add zblock allocator Message-ID: References: <20250401171754.2686501-1-vitaly.wool@konsulko.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250401171754.2686501-1-vitaly.wool@konsulko.se> X-Migadu-Flow: FLOW_OUT X-Rspamd-Queue-Id: 9E08740009 X-Rspamd-Server: rspam05 X-Rspam-User: X-Stat-Signature: z4s6txi46yk7uarxkg5d9h7jm88tgwam X-HE-Tag: 1743549395-514654 X-HE-Meta: U2FsdGVkX1/AdbIodTcS50pW2zaqAqAIr64aTMkan5ApuNZ8DbVvJ4DFmKUhfrvbmMUY02dL7ojfa5G6N/zVEof4/mkfzfIY54KkudUz8yes+aE+OMPN2btZP0QO2EM8pcufXP2Pn3subFU55TJo9qXcr1WxrCFvaSoFD67r2BzNM2gRrK36MXhToJg0jyc6BdEL/E/yN9z9/Bc1/mvkgO3e6yQU671gwiSGQML6h7CTMbgrvHhzBbbgcZPL8KNbfTcOgADiAnYdWjcToj7Mf85GxlltIwh6sqTxj9NO3VNwFYJg/okrShC36ZQEP8L/bZ3mUtu71HFGt3EhDc4drBLRiqTlqvxgqJiV7B3rPmyIq3HantN1WKkMXIaQI08acAgLFiCaBOVNl9yICDkYDNmxVpi77u7ejupoyk+Zi5VcjU76ZgNomLRCd6geRk07rftdxNutijQ6cDFxyPKBnAV8QfJe8ih5yT0C5laeaF/p5I4dYldz+pWhpvH2dBBZUphNHQvp+u5WGb5nmg/5pGQNHmZE3EeO3ColPsmZK0DTGoUWKKzJra5Q1FXgomgmEMOJbQUf2VijUZLPuZljW8BFXdF37RZupsh2JUkl0RhXPpSV0D4VdBHbxaywGBeU8sK4c6icGU3cZU1dOurOIAUFpsG97UM6JU29GJpeakTE4tpZOs5bTYWQxvyx8TWvldeyQZRH2YiPYawTQLM9xbI5HGXLhq2PN5inK2vpwt94KycA2jIPeIJb3sgBZPS7e7gRnXN66Mj+/yAEwMvucH0AqMAlMg99wbr/PDtfHxDFJ273F18XfE2F6r8HUF6KMfvYjrgKbND50xgMMq77S4TjM4e+88i2Xejst5arWZ2O1x9eUJhbETKPCX/lEcvzCIblFPBImlADqUnoEIfhoganUZBNXsDFD5RjGXDwGWPqDkkv0rTvswZ5pOPG2wQ9pdFwrtJxJODKYN6C4b5 bwbNSXtE JJ7DHleWGEvV1b0ojXwpBb7JDStVJi9ye8lQomqJAv+08xlD/tDNtIi3LtzDYpPKat2bQXKUuMcdxcgQSwZ6NBPUFzBIcJvfkz7AjHik0FRWbEH93PXeVoZtoBCt4H6QWceqOsWjpR4YKgUD4j9BfhIwNDIxazE7zo1sBkMDWXUFPj0KDnm3m1Bb5kQ== 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: List-Subscribe: List-Unsubscribe: Hi Vitaly, On Tue, Apr 01, 2025 at 07:17:54PM +0200, Vitaly Wool wrote: > zblock is a special purpose allocator for storing compressed pages. > It stores integer number of compressed objects per its block. These > blocks consist of several physical pages (2**n, i. e. 1/2/4/8). > > With zblock, it is possible to densely arrange objects of various sizes > resulting in low internal fragmentation. Also this allocator tries to > fill incomplete blocks instead of adding new ones, in many cases > providing a compression ratio substantially higher than z3fold and zbud > (though lower than zmalloc's). > > zblock does not require MMU Can you explain why not requiring MMU is important for your use-case? Also what exactly is your use-case? Are you planning to use zblock through zram or zswap or something new? > to operate and also is superior to zsmalloc > with regard to average performance and worst execution times, thus > allowing for better response time and real-time characteristics of the > whole system. > > E. g. on a series of stress-ng tests run on a Raspberry Pi 5, we get > 5-10% higher value for bogo ops/s in zblock/zsmalloc comparison. Can you explain a bit more on this test? How is this test using zblock? thanks, Shakeel