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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 53CF1C47077 for ; Tue, 16 Jan 2024 21:01:03 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=chrisdown.name header.i=@chrisdown.name header.a=rsa-sha256 header.s=google header.b=ObpAGtxi; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4TF1d96lGVz3c20 for ; Wed, 17 Jan 2024 08:01:01 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=chrisdown.name header.i=@chrisdown.name header.a=rsa-sha256 header.s=google header.b=ObpAGtxi; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=chrisdown.name (client-ip=2a00:1450:4864:20::42c; helo=mail-wr1-x42c.google.com; envelope-from=chris@chrisdown.name; receiver=lists.ozlabs.org) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4TDw070stPz2yVR for ; Wed, 17 Jan 2024 03:47:02 +1100 (AEDT) Received: by mail-wr1-x42c.google.com with SMTP id ffacd0b85a97d-337b71a0240so643133f8f.0 for ; Tue, 16 Jan 2024 08:47:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; t=1705423619; x=1706028419; darn=lists.ozlabs.org; h=user-agent: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=3ogzn1QqBOwM6/wPLFbgIITGAg256qwJXlVYrohCZ+U=; b=ObpAGtxiaEedjiL7AVFUX1gsl2p25B3LLEMFquULG3lW2F5qzjy+AUWjjWMvk3BdBn UdMqAQYAWUcLZWYbh9433+E7H+mnbt8xp1qCIrq982EbALTpxZ2K03zIZkSv7yfdc1A0 f0ySlcHFSUQNm7EhJBbPZkdrNnY2xwCrTGkbo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705423619; x=1706028419; h=user-agent: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=3ogzn1QqBOwM6/wPLFbgIITGAg256qwJXlVYrohCZ+U=; b=qTIQmKrMQU7Ns0cKruoXojWBAq4BMZsmWBXFDg2IUZWL9pIz1SsKv9VZPPNcxoQNbD HqPNI8Zp4qN8Mc5WQI1tFjizeKD6uL813LjBob/xpS7EK9mDXKQA4tgg6/Q8hu69rWmC 7hgh5BGdj+hAbnefBIXL0cJOqy6HS0WFAEsxjBOTtlD0tbt6sn0EMeMYkFU1UISuDbdp dn5FGQ6UK3O/7+F0QL5rineIkHEb/3lCSDtdwZezRCSROsD1Qf6tcDHRtDnTxTVddBYn euFs/f5lkaNOzgIDVOSEjNy1l3IP6b43J43IkC2EMMqTYWP4VAtZr2hboajSdlkQPqhn /hoA== X-Gm-Message-State: AOJu0YynMPc9vtjQJD5atRSuIjko57keD60iM7uqvrVq4qCQBrHwzebT KWpJEXj+lHKHpiGzM5oMQtVDqsgqy0CDTQ== X-Google-Smtp-Source: AGHT+IHTwTfXe8Kw9MMMyJkn57jMIAuA/0iSLfegMtL87aQGeeTMAiAXO0QSXc2/GrfW77hv7V8JoQ== X-Received: by 2002:adf:fcd1:0:b0:337:90e3:d66 with SMTP id f17-20020adffcd1000000b0033790e30d66mr4545484wrs.51.1705423619004; Tue, 16 Jan 2024 08:46:59 -0800 (PST) Received: from localhost ([2a01:4b00:8432:8600:5ee4:2aff:fe50:f48d]) by smtp.gmail.com with ESMTPSA id v3-20020adfedc3000000b00337bcbd0968sm1637227wro.104.2024.01.16.08.46.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jan 2024 08:46:58 -0800 (PST) Date: Tue, 16 Jan 2024 16:46:57 +0000 From: Chris Down To: Vitaly Wool Subject: Re: [RFC PATCH] mm: z3fold: rename CONFIG_Z3FOLD to CONFIG_Z3FOLD_DEPRECATED Message-ID: References: <20240112193103.3798287-1-yosryahmed@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) X-Mailman-Approved-At: Wed, 17 Jan 2024 07:59:26 +1100 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Miaohe Lin , "Aneesh Kumar K.V" , Nhat Pham , Huacai Chen , Nicholas Piggin , Yosry Ahmed , linux-mm@kvack.org, loongarch@lists.linux.dev, Johannes Weiner , "Naveen N. Rao" , Andrew Morton , linuxppc-dev@lists.ozlabs.org, WANG Xuerui Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Vitaly Wool writes: >> Existing users, if any, should voice their objections. Otherwise, we can >> remove z3fold in a few releases. > >At this point I NACK this patch. We're about to submit an allocator >which is clearly better that z3fold and is faster that zsmalloc in >most cases and that submission will mark z3fold as deprecated. But for >now this move is premature. Why should that block completely unrelated cleanup work? Let's please not add dependencies between patches when there don't need to be.