From patchwork Thu Oct 27 04:26:42 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Sergey Senozhatsky X-Patchwork-Id: 13021571 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 85794C67871 for ; Thu, 27 Oct 2022 04:26:59 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F15868E0002; Thu, 27 Oct 2022 00:26:58 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EC5CF8E0001; Thu, 27 Oct 2022 00:26:58 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DB4BC8E0002; Thu, 27 Oct 2022 00:26:58 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id CCAC98E0001 for ; Thu, 27 Oct 2022 00:26:58 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 9A68AA1086 for ; Thu, 27 Oct 2022 04:26:58 +0000 (UTC) X-FDA: 80065444116.01.D1BE64E Received: from mail-pj1-f46.google.com (mail-pj1-f46.google.com [209.85.216.46]) by imf26.hostedemail.com (Postfix) with ESMTP id 301FE140005 for ; Thu, 27 Oct 2022 04:26:57 +0000 (UTC) Received: by mail-pj1-f46.google.com with SMTP id u8-20020a17090a5e4800b002106dcdd4a0so5108470pji.1 for ; Wed, 26 Oct 2022 21:26:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=sLpRMNQkYbVj6lyrmRrOxuuwmgiytFPuZn2IVFPntgM=; b=h0chSoTr9LjZO+zENyYG/Z5Q+FKzIaov9HQFxUG64gBu+2GKz2R/9u3u7+0MU7R0wt vlHlWa+fYEWocbNl7x13wdFDgrbF00lwqinD3Zy6lyfAqx3xQPrUO/ffW5tSXdn0Ca8O Yyvq6cq3UbLn/hUgrAJYeuLOza1Wv9SvmKomk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sLpRMNQkYbVj6lyrmRrOxuuwmgiytFPuZn2IVFPntgM=; b=zN076wPdPfofIKfPwAVITD1i3rCLqB1PIcbPEbJ2wroYbcQTZTpXI83J1LzRluWDgf UKfvqihIM6ydc97KfaanheDXA0OovTFQenJYay6Gs7PlfiHusFsKsC4EXLyoK2J4J08j jTP2olBOUZUxYqzgQT3tlvqc7hjEoIvIvA3Wl03cr0OLtQDy4l7eyYP/2h3T2WnMt4ez pA+2KM1/z8fKRcMwRXgaKhXERhikSYN+VA5ohG0LqdenGfToBhA01LTTDohA0vF77+b3 BdFdDCZn/sSOhSTWr8pDvUuxZD6FvLbG9EjvX5vw0N2t1vMwxYJulnkK1LHpyf7zn9KV U6Hw== X-Gm-Message-State: ACrzQf0uesNsmJv0i4M43w427k/PQP9IznN7ViM+9npvyN/ezrErvwkZ TcyR9UqInDPwqaYudVk+YfS7ew== X-Google-Smtp-Source: AMsMyM7ej7d6DvNI5V90T+YskrHYFramiQG9gIeKgZ32QfvvxlFWmQ4IoOb5JP8QfhN8qhwkK7U9EQ== X-Received: by 2002:a17:902:848c:b0:17a:b4c0:a02b with SMTP id c12-20020a170902848c00b0017ab4c0a02bmr47126465plo.122.1666844816979; Wed, 26 Oct 2022 21:26:56 -0700 (PDT) Received: from tigerii.tok.corp.google.com ([2401:fa00:8f:203:30f2:4501:65fa:df12]) by smtp.gmail.com with ESMTPSA id w23-20020aa79557000000b00565c8634e55sm203140pfq.135.2022.10.26.21.26.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Oct 2022 21:26:56 -0700 (PDT) From: Sergey Senozhatsky To: Andrew Morton , Minchan Kim Cc: Nitin Gupta , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Sergey Senozhatsky Subject: [PATCHv3 0/9] zsmalloc/zram: configurable zspage size Date: Thu, 27 Oct 2022 13:26:42 +0900 Message-Id: <20221027042651.234524-1-senozhatsky@chromium.org> X-Mailer: git-send-email 2.38.0.135.g90850a2211-goog MIME-Version: 1.0 ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1666844818; a=rsa-sha256; cv=none; b=gOEp749tXvZIWxV/deptuv11AQ5isMxNR2mceQx4IF8u2frdjjj14JiZbdvbKmKs5hjY8W H6Eb/lDWb+JfWwlShuqfRwpyfu46MwmKqM1XkYrvwX/aRzF2k2nz6vwMHdx9ITrr6xujZJ WVMZJ9qluJCKdd5rNsI/Is4clAQJOpE= ARC-Authentication-Results: i=1; imf26.hostedemail.com; dkim=pass header.d=chromium.org header.s=google header.b=h0chSoTr; dmarc=pass (policy=none) header.from=chromium.org; spf=pass (imf26.hostedemail.com: domain of senozhatsky@chromium.org designates 209.85.216.46 as permitted sender) smtp.mailfrom=senozhatsky@chromium.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1666844818; 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-transfer-encoding:content-transfer-encoding: in-reply-to:references:dkim-signature; bh=sLpRMNQkYbVj6lyrmRrOxuuwmgiytFPuZn2IVFPntgM=; b=E1wlk7m0/VKE2A3w1ZZRjZG9/0jbYyL5DmJle/GkKLLr6dfE/Qh0BFdluKR9dVahCfXLOl lhnyxR3W8T2TIFr6MqShZd8NI9pHzgBGwmctN3RNDa6U5b8/BJQES3Svo3Q/2UCk1v7YyZ M1uLxoMVzOcWApdqJZdGtIHOXIMkYjo= X-Rspam-User: Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=chromium.org header.s=google header.b=h0chSoTr; dmarc=pass (policy=none) header.from=chromium.org; spf=pass (imf26.hostedemail.com: domain of senozhatsky@chromium.org designates 209.85.216.46 as permitted sender) smtp.mailfrom=senozhatsky@chromium.org X-Rspamd-Server: rspam11 X-Stat-Signature: tywqkmzyr8836nakytpz1watyoehqrq8 X-Rspamd-Queue-Id: 301FE140005 X-HE-Tag: 1666844817-572900 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: Hello, Some use-cases and/or data patterns may benefit from larger zspages. Currently the limit on the number of physical pages that are linked into a zspage is hardcoded to 4. Higher limit changes key characteristics of a number of the size classes, improving compactness of the pool and redusing the amount of memory zsmalloc pool uses. More on this in 0001 commit message. v3: -- Removed lots of text from 0001 commit message. Now it's shorter and simpler. v2: -- Cherry picked a patch from Alexey (minor code tweaks to move it ahead of this series) -- zsmalloc does not require anymore pages-per-zspage limit to be a pow of 2 value, and overall doesn't use "order" any longer -- zram does not require "zspage order" (pow of 2) value anymore and instead accepts an integer in [1,16] range -- There is no global huge_class_size in zsmalloc anymore. huge_class_size is per-pool, since it depends on pager-per-zspage, which can be different for different pools. -- There is no global huge_class_size in zram anymore. It should be per-pool (per-device). -- Updated documentation -- Fixed documentation htmldocs warning (Stephen) -- Dropped get_pages_per_zspage() patch -- Renamed zram sysfs knob (device attribute) -- Re-worked "synthetic test" section in the first commit: more numbers, objects distribution analysis, etc. Alexey Romanov (1): zram: add size class equals check into recompression Sergey Senozhatsky (8): zsmalloc: turn zspage order into runtime variable zsmalloc: move away from page order defines zsmalloc: make huge class watermark zs_pool member zram: huge size watermark cannot be global zsmalloc: pass limit on pages per-zspage to zs_create_pool() zram: add pages_per_pool_page device attribute Documentation: document zram pages_per_pool_page attribute zsmalloc: break out of loop when found perfect zspage order Documentation/admin-guide/blockdev/zram.rst | 38 +++++-- drivers/block/zram/zram_drv.c | 63 +++++++++-- drivers/block/zram/zram_drv.h | 7 ++ include/linux/zsmalloc.h | 14 ++- mm/zsmalloc.c | 114 +++++++++++++------- 5 files changed, 178 insertions(+), 58 deletions(-)