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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 22935C00A89 for ; Thu, 5 Nov 2020 07:37:48 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 982C620936 for ; Thu, 5 Nov 2020 07:37:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="naoojfVx" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 982C620936 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject: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=1dLCzGVGZyBcDsOcGqe48s4XZ7l1Mtzpped93lQBg7k=; b=naoojfVxPwb9kQjOHlr6tXzTG 7AUqMY0pkHgrEUhcCRzu8fDnxcBmIi4SaaccIbeZmCwt++UJpXCHjpCpxoofzA8Z8qyyHCll6BL8S qQCOPYV5EhykI7FMNDICV5XXezPGw5amRvsJaz1k1KgkqwqIFsBBZzRW8ZeHxSJlyLMZ0LMVQrwDZ FAmlrORaIIwb0QD6kGVjxOX1kS7t3gbzBT2mo7g9w3RRnjt75WFPSJ4C82KGuEeHLc97jkoUzQ/KD zemkFB1j5/p7Ikr7qzxf9ccBj22QgxjAXgf40Vm6fWMzDRYy7afhN7zemXw0CCmCJDt85SS4eGePq K8n62DPOA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kaZq3-0004gy-Cf; Thu, 05 Nov 2020 07:37:43 +0000 Received: from verein.lst.de ([213.95.11.211]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kaZq0-0004g0-Kq for linux-nvme@lists.infradead.org; Thu, 05 Nov 2020 07:37:41 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id B57DD68B02; Thu, 5 Nov 2020 08:37:37 +0100 (CET) Date: Thu, 5 Nov 2020 08:37:37 +0100 From: "hch@lst.de" To: Hannes Reinecke Subject: Re: [PATCH V2] nvme: report capacity 0 for non supported ZNS SSDs Message-ID: <20201105073737.GA4747@lst.de> References: <0916865d50c640e3aa95dc542f3986b9@CAMSVWEXC01.scsc.local> <20201102180836.GC20182@lst.de> <20201102183355.GB1970293@dhcp-10-100-145-180.wdc.com> <20201102185851.GA21349@lst.de> <23e10fd1-d20c-cf77-4dc0-dd8b0774fd7a@suse.de> <20201104142908.GA7941@lst.de> <01c72262-1839-05cc-ba9a-94b260511a7c@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <01c72262-1839-05cc-ba9a-94b260511a7c@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201105_023740_843750_95DC9AA2 X-CRM114-Status: UNSURE ( 9.40 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "axboe@kernel.dk" , "Niklas.Cassel@wdc.com" , "javier@javigon.com" , "sagi@grimberg.me" , "joshi.k@samsung.com" , "Klaus B. Jensen" , "linux-nvme@lists.infradead.org" , "linux-block@vger.kernel.org" , Keith Busch , Javier Gonzalez , "hch@lst.de" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Wed, Nov 04, 2020 at 03:46:02PM +0100, Hannes Reinecke wrote: > ... as would a bsg device which could accept said ioctl ... Sure we could. So we'd have to add more code to almost 1000 lines of code in bsg that are not useful to the nvme use case to make it useful for that use case. Or we could just add about 50 lines of code to NVMe to do the right thing. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme