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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 187F2C433EF for ; Tue, 15 Mar 2022 17:01:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=slXPPIwOr/e+nHDO1AyOwiyeK0RtqT4vlXauKr5bsUE=; b=Nr+nFfV4sc0xmpG7kJtEU+aIdT 0D9lHsPfC3wzmooaKrEbQKxl8VABpnTQMjBCgBgqeEPGnRa6d7dF4dBTEwK5d7ve3t9uFaQgyCHX6 SHqTEKqsoBizSYq/LFrgvFJE9aAZOdWZWKM/LFulh65Lj1/L7T5MSrKxg05YxzRT/ZS2ZhCw6JUgG X8i+BBDiAar1trVl7l6iKcuVje2a/IvEn/R+VUQoBWlgGPa2ChnmWqL4mVJCCAqLF1/3FaKR3upt/ YE8E/GFxYke8FZDr1GJzXW15Nf/Jg6M4wDcT8BGvuldZesCOJVnkCOycX+3N76rJCWfBxaevKPYB8 6+CjePUA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nUAXd-009y9O-Pa; Tue, 15 Mar 2022 17:01:04 +0000 Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nUAXb-009y8M-JY; Tue, 15 Mar 2022 17:00:59 +0000 Date: Tue, 15 Mar 2022 10:00:59 -0700 From: Luis Chamberlain To: Christoph Hellwig Cc: Javier =?iso-8859-1?Q?Gonz=E1lez?= , Matias =?iso-8859-1?Q?Bj=F8rling?= , Damien Le Moal , Keith Busch , Pankaj Raghav , Adam Manzanares , "jiangbo.365@bytedance.com" , kanchan Joshi , Jens Axboe , Sagi Grimberg , Pankaj Raghav , Kanchan Joshi , "linux-block@vger.kernel.org" , "linux-nvme@lists.infradead.org" Subject: Re: [PATCH 0/6] power_of_2 emulation support for NVMe ZNS devices Message-ID: References: <20220314073537.GA4204@lst.de> <05a1fde2-12bd-1059-6177-2291307dbd8d@opensource.wdc.com> <20220314104938.hv26bf5vah4x32c2@ArmHalley.local> <20220314195551.sbwkksv33ylhlyx2@ArmHalley.local> <20220315130501.q7fjpqzutadadfu3@ArmHalley.localdomain> <20220315132611.g5ert4tzuxgi7qd5@unifi> <20220315133052.GA12593@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220315133052.GA12593@lst.de> X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Tue, Mar 15, 2022 at 02:30:52PM +0100, Christoph Hellwig wrote: > On Tue, Mar 15, 2022 at 02:26:11PM +0100, Javier González wrote: > > but we do not see a usage for ZNS in F2FS, as it is a mobile > > file-system. As other interfaces arrive, this work will become natural. > > > > ZoneFS and butrfs are good targets for ZNS and these we can do. I would > > still do the work in phases to make sure we have enough early feedback > > from the community. > > > > Since this thread has been very active, I will wait some time for > > Christoph and others to catch up before we start sending code. > > Can someone summarize where we stand? RFCs should be posted to help review and evaluate direct NPO2 support (not emulation) given we have no vendor willing to take a position that NPO2 will *never* be supported on ZNS, and its not clear yet how many vendors other than Samsung actually require NPO2 support. The other reason is existing NPO2 customers currently cake in hacks to Linux to supoport NPO2 support, and so a fragmentation already exists. To help address this it's best to evaluate what the world of NPO2 support would look like and put the effort to do the work for that and review that. Luis