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 us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 D36FDC433EF for ; Tue, 17 May 2022 08:11:02 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-155-FuD0e62uNMWbVLOLl6BrWw-1; Tue, 17 May 2022 04:10:58 -0400 X-MC-Unique: FuD0e62uNMWbVLOLl6BrWw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 08BE5100BAA0; Tue, 17 May 2022 08:10:57 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id B23E840CF8F0; Tue, 17 May 2022 08:10:56 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 7C1221947060; Tue, 17 May 2022 08:10:56 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id C43691947060 for ; Tue, 17 May 2022 08:10:54 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id A555A403156; Tue, 17 May 2022 08:10:54 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast05.extmail.prod.ext.rdu2.redhat.com [10.11.55.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A1C79492C14 for ; Tue, 17 May 2022 08:10:54 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 8D0AF833965 for ; Tue, 17 May 2022 08:10:54 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-203-q5c0yKkgMAiKXNglnk8yOQ-1; Tue, 17 May 2022 04:10:52 -0400 X-MC-Unique: q5c0yKkgMAiKXNglnk8yOQ-1 Received: by verein.lst.de (Postfix, from userid 2407) id B1EFE67373; Tue, 17 May 2022 10:10:48 +0200 (CEST) Date: Tue, 17 May 2022 10:10:48 +0200 From: Christoph Hellwig To: Pankaj Raghav Message-ID: <20220517081048.GA13947@lst.de> References: <20220516165416.171196-1-p.raghav@samsung.com> MIME-Version: 1.0 In-Reply-To: <20220516165416.171196-1-p.raghav@samsung.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 Subject: Re: [dm-devel] [PATCH v4 00/13] support non power of 2 zoned devices X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: axboe@kernel.dk, pankydev8@gmail.com, gost.dev@samsung.com, damien.lemoal@opensource.wdc.com, jiangbo.365@bytedance.com, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, dm-devel@redhat.com, dsterba@suse.com, hch@lst.de, linux-btrfs@vger.kernel.org Errors-To: dm-devel-bounces@redhat.com Sender: "dm-devel" X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm a little surprised about all this activity. I though the conclusion at LSF/MM was that for Linux itself there is very little benefit in supporting this scheme. It will massively fragment the supported based of devices and applications, while only having the benefit of supporting some Samsung legacy devices. So my impression was that this work, while technically feasible, is rather useless. So unless I missed something important I have no interest in supporting this in NVMe. -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel 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 CE88BC433EF for ; Tue, 17 May 2022 08:11:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230219AbiEQIL6 (ORCPT ); Tue, 17 May 2022 04:11:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34518 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242566AbiEQIK4 (ORCPT ); Tue, 17 May 2022 04:10:56 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9C4E72BF2; Tue, 17 May 2022 01:10:52 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id B1EFE67373; Tue, 17 May 2022 10:10:48 +0200 (CEST) Date: Tue, 17 May 2022 10:10:48 +0200 From: Christoph Hellwig To: Pankaj Raghav Cc: axboe@kernel.dk, damien.lemoal@opensource.wdc.com, pankydev8@gmail.com, dsterba@suse.com, hch@lst.de, 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: <20220517081048.GA13947@lst.de> References: <20220516165416.171196-1-p.raghav@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220516165416.171196-1-p.raghav@samsung.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org I'm a little surprised about all this activity. I though the conclusion at LSF/MM was that for Linux itself there is very little benefit in supporting this scheme. It will massively fragment the supported based of devices and applications, while only having the benefit of supporting some Samsung legacy devices. So my impression was that this work, while technically feasible, is rather useless. So unless I missed something important I have no interest in supporting this in NVMe.