Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp1491866rwb; Sat, 14 Jan 2023 22:20:40 -0800 (PST) X-Google-Smtp-Source: AMrXdXuxoJDG8LUzGQHdhU+u2cpIWplKPeK5/DOPW+eYgEWudPY0foSWxAsaxNedpa/soYUEUPhV X-Received: by 2002:aa7:de9a:0:b0:49b:53db:5766 with SMTP id j26-20020aa7de9a000000b0049b53db5766mr12921422edv.35.1673763640509; Sat, 14 Jan 2023 22:20:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673763640; cv=none; d=google.com; s=arc-20160816; b=LP+6KJ4UTRBU5cR3KVsjPEKSTB8XjXX+Th2SRmCngtwQTNhMSQDbr1u2mTbx3Mb1UA aNsTdWCqXoBivQEvDWSo3eo/MLjxLPiT3rAek2A6UJc3Vyw4bTlhMtl5vzwJezT0GXB6 NQ2SJekBjSNZU32DLIpBDnAOW0lhzUGOitFydl8pEtfyzaGquNVRj+OrU8FOsZcfHcq9 LOo+vaIhkOPaw6OxGg0jGwZHh3lLZ3LLe3b08ddd9EznWsFFqf3IqEtIS2zqOJz1sZcP NFevbHPgvqM7nx6CFx7RcXGZNYvQZZxhYmi3rcDk1dcVFC9PzB9N7kX/zs2ziWKDPQnx wkvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=6pV+Lc/D2szFMSqw+ADbk9E95BAdnQD4U8oWvWD9EP0=; b=tST6PvXy1EcnwOtDhxjLKu/sOkPnH2hDNiuXNaFJX5dH0G+EiGAIs8SoUYtupMmlpp TJj2G8VQJ8pSaQ5auE8EVGdTjLLwMrY1/V+7CY5U87merVMgM5SZ9xTQEKF7a1c4Fetj Rnl0x1AddWjwOvQA1kOhENw05Jh2yHA4fMkSp6BfuRoxscTwCGUTN7NhepXxyvnzT/cI kLe5KkaKbzx/F2gtMbdnLp5sukOQ//5OHcJ1K4xSCSJ8Ra/kE2BqIo6JGsU74yf3bw1L zYVPKyefZ8ralq/2+J6f0w+8fImp7MkQFbinIrOglSx7BT3LXxb7KOh3iaS1Sj8Jh1FA rqoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=UsjVTg8U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w19-20020a05640234d300b0046b7410c015si30832797edc.18.2023.01.14.22.20.20; Sat, 14 Jan 2023 22:20:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=UsjVTg8U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230488AbjAOFc6 (ORCPT + 54 others); Sun, 15 Jan 2023 00:32:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230344AbjAOFc4 (ORCPT ); Sun, 15 Jan 2023 00:32:56 -0500 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E1C8EBBB6 for ; Sat, 14 Jan 2023 21:32:55 -0800 (PST) Received: by mail-pj1-x1034.google.com with SMTP id q23-20020a17090a065700b002290913a521so8678336pje.5 for ; Sat, 14 Jan 2023 21:32:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=6pV+Lc/D2szFMSqw+ADbk9E95BAdnQD4U8oWvWD9EP0=; b=UsjVTg8UKzR4bqwwTKuexbqPD1K8c7rYDjqkBdbFTSxrx2z6wdrNX0rYuViUtvpSLV aaTQxaoUuT4GWrqxIzEBSwTzVfq97lPKXME7jRoptzIp/axAt1lrlRmLuOo5bQrVrS4a GJLrzFIf55B1ja1GDXVtB6vuIGHlmafdSBUCM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=6pV+Lc/D2szFMSqw+ADbk9E95BAdnQD4U8oWvWD9EP0=; b=3FJ/YEAAcEJff09xnNtRMoEdFPiAt8IE6KbwqPcaVO2DuZhnyYljnt8/yO0uT0fVD1 Owukr5RXVAXo8vkF574xBqPOmsDVqRpyxL7xcHdWI/yIvU8BdwFRWCNoSzkQJngftEF6 FccpQAtl5mKuuNDEE9FH4qgCdCO6cb4MwG+0vo9pjh8fe8MR1UoTkGQFAPsccu3jsiOb WKjxUgmDvKLqN9PuKTKQu2HlaAi0wkXUonu+9mHx1PvxB4EU9LjM+CP2NJWeJ5rgs9Bc u187so9EG9Ugb8OpWiviP/psOR5YohomnIQDWoW2TR10n7O6B3SHlrJp4rsHzvQEOE9s npag== X-Gm-Message-State: AFqh2kpaDpHjTVpZUu4m/ji4l6YIJV8GcWEFoAdAQ7Y/iHBQ58HrauRY AjSgp9B7XkXfmGk2VfS+1tXrUg== X-Received: by 2002:a17:902:ccc5:b0:185:441e:4cfc with SMTP id z5-20020a170902ccc500b00185441e4cfcmr100561742ple.44.1673760775240; Sat, 14 Jan 2023 21:32:55 -0800 (PST) Received: from google.com (KD124209188001.ppp-bb.dion.ne.jp. [124.209.188.1]) by smtp.gmail.com with ESMTPSA id s1-20020a170902ea0100b001913c5fc051sm5646253plg.274.2023.01.14.21.32.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 Jan 2023 21:32:54 -0800 (PST) Date: Sun, 15 Jan 2023 14:32:50 +0900 From: Sergey Senozhatsky To: Mike Kravetz Cc: Minchan Kim , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Sergey Senozhatsky Subject: Re: [PATCHv2 0/4] zsmalloc: make zspage chain size configurable Message-ID: References: <20230109033838.2779902-1-senozhatsky@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (23/01/15 13:21), Sergey Senozhatsky wrote: > On (23/01/14 13:34), Mike Kravetz wrote: > > I did the following: > > > > - Start with clean v6.2-rc3 > > Perform echo, did not see issue > > > > - Applied your 5 patches (includes the zsmalloc: turn chain size config option > > into UL constant patch). Took default value for ZSMALLOC_CHAIN_SIZE of 8. > > Performed echo, recreated issue. > > > > - Changed ZSMALLOC_CHAIN_SIZE to 1. > > Perform echo, did not see issue > > The patch set basically just adjusts $NUM in calculate_zspage_chain_size(): > > for (i = 1; i <= $NUM; i++) > > It changes default 4 to 8. Can't really see how this can cause problems. OK, I guess it overflows zspage isolated counter, which is a 3 bit integer, so the max chain-size we can have is b111 == 7. We probably need something like below (this should not increase sizeof zspage): --- diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c index 290053e648b0..86b742a613ee 100644 --- a/mm/zsmalloc.c +++ b/mm/zsmalloc.c @@ -129,7 +129,7 @@ #define HUGE_BITS 1 #define FULLNESS_BITS 2 #define CLASS_BITS 8 -#define ISOLATED_BITS 3 +#define ISOLATED_BITS 5 #define MAGIC_VAL_BITS 8 #define MAX(a, b) ((a) >= (b) ? (a) : (b))