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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4BEE4C433EF for ; Wed, 18 May 2022 08:00:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232997AbiERIAg (ORCPT ); Wed, 18 May 2022 04:00:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32860 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232861AbiERIAf (ORCPT ); Wed, 18 May 2022 04:00:35 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 30FE212719D; Wed, 18 May 2022 01:00:34 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id C8B2D68C7B; Wed, 18 May 2022 10:00:22 +0200 (CEST) Date: Wed, 18 May 2022 10:00:20 +0200 From: Christoph Hellwig To: Javier =?iso-8859-1?Q?Gonz=E1lez?= Cc: Christoph Hellwig , Pankaj Raghav , axboe@kernel.dk, damien.lemoal@opensource.wdc.com, pankydev8@gmail.com, dsterba@suse.com, linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org, jiangbo.365@bytedance.com, linux-block@vger.kernel.org, gost.dev@samsung.com, linux-kernel@vger.kernel.org, dm-devel@redhat.com Subject: Re: [PATCH v4 00/13] support non power of 2 zoned devices Message-ID: <20220518080020.GA3697@lst.de> References: <20220516165416.171196-1-p.raghav@samsung.com> <20220517081048.GA13947@lst.de> <20220517091834.dvkrab5l63v3b2zn@ArmHalley.local> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220517091834.dvkrab5l63v3b2zn@ArmHalley.local> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 17, 2022 at 11:18:34AM +0200, Javier González wrote: > Does the above help you reconsidering your interest in supporting this > in NVMe? Very little. It just seems like a really bad idea.