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 A37D5C02190 for ; Thu, 30 Jan 2025 16:27:47 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1EF9E440151; Thu, 30 Jan 2025 11:27:47 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1792E28028F; Thu, 30 Jan 2025 11:27:47 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 01A47440151; Thu, 30 Jan 2025 11:27:46 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id D5DCA28028F for ; Thu, 30 Jan 2025 11:27:46 -0500 (EST) Received: from smtpin26.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 63CBC8014D for ; Thu, 30 Jan 2025 16:27:46 +0000 (UTC) X-FDA: 83064649332.26.254AD4C Received: from out-176.mta1.migadu.com (out-176.mta1.migadu.com [95.215.58.176]) by imf22.hostedemail.com (Postfix) with ESMTP id 5D579C0020 for ; Thu, 30 Jan 2025 16:27:44 +0000 (UTC) Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=xxiOhWk5; dmarc=pass (policy=none) header.from=linux.dev; spf=pass (imf22.hostedemail.com: domain of yosry.ahmed@linux.dev designates 95.215.58.176 as permitted sender) smtp.mailfrom=yosry.ahmed@linux.dev ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1738254464; a=rsa-sha256; cv=none; b=iNnJcwvDpyf9uzdhVRgS6ZyBOqPGQa2DTSZe+jDuuDCrhavk70DLa1LWBs0JHav0+cC7VB Ng9+rjLxfXkWZ/MhAmIsXskFZ+PxOzJ4m1Vez12wYLpB5ycOQIasKKNmeU05W2zWRl41OM jXo1Sm05FVbaae7x+Rp9Jv/8PXI/Z/Y= ARC-Authentication-Results: i=1; imf22.hostedemail.com; dkim=pass header.d=linux.dev header.s=key1 header.b=xxiOhWk5; dmarc=pass (policy=none) header.from=linux.dev; spf=pass (imf22.hostedemail.com: domain of yosry.ahmed@linux.dev designates 95.215.58.176 as permitted sender) smtp.mailfrom=yosry.ahmed@linux.dev ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1738254464; 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=ujaI8pRfjL8nb8oaU9SuzdWjLjHuAQvmbrJdAwmlxfI=; b=zKbQbFFsyvKHojqTRi7qBZO1F5zsoilyq/EN99KoaCXhTKW4sdPf4t7uX4iuw9DLzvzNCO gU3rhSZQhnxuYyDRwpVrmrhCIFgjIlu2DVz7wExZk2nMhCD8BBxC4EyHaY0WpPIJbdUS00 0MyzHIcmJ5Rm3eNtcJO5xp1VAMSwexE= Date: Thu, 30 Jan 2025 16:27:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1738254462; 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=ujaI8pRfjL8nb8oaU9SuzdWjLjHuAQvmbrJdAwmlxfI=; b=xxiOhWk5vZkVkrGjeRv1dR8sviL3nj+1t8Lrnw2NgAETePewLAzd2si8k2b4LvCsdS7SCB rNHidEitfqRyhtsb2z0BU8ur3LBYEZNaN9KXU0uAQnIILnCjerskalJqribJs0SIq7ibUP qq1G8GEd5ZwX9se8umXuUeYBpgx15e4= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Yosry Ahmed To: Sergey Senozhatsky Cc: Andrew Morton , Minchan Kim , Johannes Weiner , Nhat Pham , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCHv1 4/6] zsmalloc: introduce new object mapping API Message-ID: References: <20250129064853.2210753-1-senozhatsky@chromium.org> <20250129064853.2210753-5-senozhatsky@chromium.org> <4slya4kbgfvkvlgkvwep2cgghs233lfhfpctfrrgvho4fpgzwr@cjp643bd4ml6> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4slya4kbgfvkvlgkvwep2cgghs233lfhfpctfrrgvho4fpgzwr@cjp643bd4ml6> X-Migadu-Flow: FLOW_OUT X-Rspam-User: X-Rspamd-Queue-Id: 5D579C0020 X-Rspamd-Server: rspam10 X-Stat-Signature: qo8xw1nqgo48q77tapkcd4jt1qrte9md X-HE-Tag: 1738254464-849117 X-HE-Meta: U2FsdGVkX1/9ieMMWZfW1vQFVo6QzdyR+i9+wCVPM9XW5SsmWMww3l64nP/QD1XkafXQjP4ArRsYH86aHBNNVRdzt9PFAEILCBEkhSEfSNDgzNJjw0Dq1HVH7taaajMiTiuFgjjME1yEKTJL12vFYkeMUvoCNzUB+Kim6N/Q0sprqvjTJ/7rdBqUZwi6OfKO9KyiZMNpMNLw8C45Lpv5meQOB4MA5Xqz/As0wvaASnyXf+Z+K65VjBH9jwmTKZ+yElSWNOhm/PiA1r88QSQxvRMkejg4BnVK8UiGAeHWwjVNbe71GUIycWlMgTz6/dSfxGAYSzDctfVsZvfPNn3sPnmx36piZQs3FU3GVmHwkvOP39paoHQ7EkV2tu4rKS66n8SHEHGnoiwEAe0IvJwRJRdjCmYn6Wa6yAifeqxhu34v3u35v5DYWDAJVl+/nRPOtGQ43d/9ylqsHpctdm8TYiLRvcyeL7eOF1vdbeQ/wuCPdOjkbWhJhfKmnlDmK87bJ6G2rg+KG3OEZYcGnqIi/OIUOpjrhkubOfAfDnZnjM3G+WNZAhzgO3h/GQPQy5efF370VJAaotWOTsRKARgrt/36DKsJgSk1eGnu6uSH58yDsagbLcw2mUEDQScsc8ij+RsNb0MLume5LI1FcrXe3AbWzzU7maspBP30AjSPs25EBCb9+OY8kkn4g08AUnPuGD9FYv6GFuJHoLkg/thhn07EAdyCqFjonBR2shPf1Y1JfUeB4KLsfe2tHegx6zqqxXQXuJDarxwfPwXAYeTv66VZre3DGIuqbnUBEKAnSc5i9mlkW6+9x9H15g9OGD8XzgvLYVx11zxc/0sOYZyMTg3BQo+DK0a63z5c5oa5KGUgMjez9Rr45K7H9vAwWKxomybeGuVQh2fY7wmOJGzO2FTyMwYTHuckOMZzUp3VjmgNY9ITre/OVbb/ljSU3cXAfKLUIo4clgKe2IFUu+f Hhr3g/BS JmCVW0HS8o7He6wjIFhBc9iVWjctDdQYtpXDSL6aU0NZHhuNOYElDBdwKgDMwtO2dD4Kp85dQ328y57AqUStIO4Mwrh5Wo5eSrHzQMcSyHM6IffaN/L+KsfMXjZ59TeWxkEGhvTpH5P/33t9hhxbrUx6ZcSCRqslep1PfKbp2neiUWiXRZlJaOV9oPR4eAa6tCKICogkJ5ZU7lWESCqpnCu9Wig== 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: On Thu, Jan 30, 2025 at 12:21:14PM +0900, Sergey Senozhatsky wrote: > On (25/01/29 17:31), Yosry Ahmed wrote: > > On Wed, Jan 29, 2025 at 03:43:50PM +0900, Sergey Senozhatsky wrote: > [..] > > > The old API will stay around until the remaining users switch > > > to the new one. After that we'll also remove zsmalloc per-CPU > > > buffer and CPU hotplug handling. > > > > I will propose removing zbud (in addition to z3fold) soon. If that gets > > in then we'd only need to update zpool and zswap code to use the new > > API. I can take care of that if you want. > > Sounds like a plan. I think I saw zbud deprecation patch (along with z3fold > removal). I guess you still want to keep zpool, just because it's there > already? Now the proposal is to remove zbud right away (patch already sent). If this lands then our lives become easier. I am keeping zpool around for now because it is not doing any harm, we can remove it later. For the zbud/z3fold their presence is a problem due to bit roting, and having to support new APIs (like this one) in them if we want to use them unconditionally in zswap.