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 8C585C433EF for ; Tue, 17 May 2022 15:36:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231463AbiEQPgf (ORCPT ); Tue, 17 May 2022 11:36:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38566 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350364AbiEQPfy (ORCPT ); Tue, 17 May 2022 11:35:54 -0400 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 26F67506D9; Tue, 17 May 2022 08:35:35 -0700 (PDT) Received: from cwcc.thunk.org (pool-108-7-220-252.bstnma.fios.verizon.net [108.7.220.252]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 24HFYsQ9026768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 May 2022 11:34:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1652801701; bh=vMDcL1Sj3ecZF/PHO33RMl8MajLs+NitzTG2owdTZQA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=QWWYv+c38E0Js5EJ5O4LH7stm0/N/0G+zlZGaxwbAbrJcoBFiFX+I8aMjlxDXtdcH HpQFgO3vNojUXJc8f+tn6qApIq1oq89uILHK6aqbgkyPptilbkipvXh8b+UDCORwcJ NTcZRZaecteMkr4C9FEtPqcOV8/1Z/mJK25oUPZYeYBBp6sBYjgpZEf9xgcokZgDBW jWBIxHO+AVv5V5gBQlM1SENquz5Y+sM7mT5fnlB7PvD9DdOkb+WioPJCoeulEVoACn ngUKDte0snQOFU95pMNMLZkRMx8s9GtBCC6kwv6i26eYPhX3g2IKwzeEwICOgNvimy LqJbC9V4JwF5A== Received: by cwcc.thunk.org (Postfix, from userid 15806) id 8636C15C3EC0; Tue, 17 May 2022 11:34:54 -0400 (EDT) Date: Tue, 17 May 2022 11:34:54 -0400 From: "Theodore Ts'o" To: Christoph Hellwig Cc: Pankaj Raghav , 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, linux-btrfs@vger.kernel.org Subject: Re: [dm-devel] [PATCH v4 00/13] support non power of 2 zoned devices Message-ID: References: <20220516165416.171196-1-p.raghav@samsung.com> <20220517081048.GA13947@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220517081048.GA13947@lst.de> Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Tue, May 17, 2022 at 10:10:48AM +0200, Christoph Hellwig wrote: > 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. FWIW, That wasn't my impression from that LSF/MM session, but once the videos become available, folks can decide for themselves. - Ted 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 E7EDBC433F5 for ; Tue, 17 May 2022 15:38:59 +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-185-jPJgO0LyO0aDvXM7U5eMfQ-1; Tue, 17 May 2022 11:38:57 -0400 X-MC-Unique: jPJgO0LyO0aDvXM7U5eMfQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B23298039D7; Tue, 17 May 2022 15:38:55 +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 97AC115088BF; Tue, 17 May 2022 15:38:17 +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 9EDFF19264E9; Tue, 17 May 2022 15:38:03 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 70D3419264E3 for ; Tue, 17 May 2022 15:38:02 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 3DF1A455922; Tue, 17 May 2022 15:38:02 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast04.extmail.prod.ext.rdu2.redhat.com [10.11.55.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 39D04455036 for ; Tue, 17 May 2022 15:38:02 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) (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 2150C101AA46 for ; Tue, 17 May 2022 15:38:02 +0000 (UTC) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-416-flCl81B7NQWciVdjbuOxng-1; Tue, 17 May 2022 11:38:00 -0400 X-MC-Unique: flCl81B7NQWciVdjbuOxng-1 Received: from cwcc.thunk.org (pool-108-7-220-252.bstnma.fios.verizon.net [108.7.220.252]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 24HFYsQ9026768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 May 2022 11:34:55 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 8636C15C3EC0; Tue, 17 May 2022 11:34:54 -0400 (EDT) Date: Tue, 17 May 2022 11:34:54 -0400 From: "Theodore Ts'o" To: Christoph Hellwig Message-ID: References: <20220516165416.171196-1-p.raghav@samsung.com> <20220517081048.GA13947@lst.de> MIME-Version: 1.0 In-Reply-To: <20220517081048.GA13947@lst.de> 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.9 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: Pankaj Raghav , 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, dsterba@suse.com, dm-devel@redhat.com, linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org Errors-To: dm-devel-bounces@redhat.com Sender: "dm-devel" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 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 On Tue, May 17, 2022 at 10:10:48AM +0200, Christoph Hellwig wrote: > 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. FWIW, That wasn't my impression from that LSF/MM session, but once the videos become available, folks can decide for themselves. - Ted -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel