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=-6.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 EA9D1C433E3 for ; Tue, 21 Jul 2020 16:11:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C8136207BB for ; Tue, 21 Jul 2020 16:11:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="GSVzJ7U/" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730234AbgGUQLe (ORCPT ); Tue, 21 Jul 2020 12:11:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726646AbgGUQLd (ORCPT ); Tue, 21 Jul 2020 12:11:33 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B0AFC061794 for ; Tue, 21 Jul 2020 09:11:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=RWiF3NwGBgrRKWnJoZttIvgTzM2rp7aYwA00ywyD1+U=; b=GSVzJ7U/2BXlo1+NyXjJAUNtfC qv9K1e5+oXyvrYIkp/hyr61zdXrwwyf89MD3WUbK6VXDnIqfDKGNSZDaGtxI22wutRHkFUZLLvCnQ XiU29kr+EANfh6FsRDIYzymc7hT6DcpQXTp+SWKYDyLkioICMrf6NO4w4bEf354VVIS5JIpz91FLR 9tKC3L/TfXX/j+KbmgVLUDygXK7JPNLm4tYZjdJusGNdMjyVFaY6XOsovlKfquIVNJPsheGtKaua+ IK8fbeLVIAC0291sVwjUTJw5eJz0PsZAhd6znAhtlypnomea01+ZnopoGrSpFYso5W+j0/rI0PmJt 0exHGgtg==; Received: from hch by casper.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1jxurY-0006V3-Q8; Tue, 21 Jul 2020 16:11:28 +0000 Date: Tue, 21 Jul 2020 17:11:28 +0100 From: Christoph Hellwig To: Johannes Thumshirn Cc: Damien Le Moal , linux-fsdevel@vger.kernel.org Subject: Re: [PATCH v4 1/2] zonefs: add zone-capacity support Message-ID: <20200721161128.GA24880@infradead.org> References: <20200721121027.23451-1-johannes.thumshirn@wdc.com> <20200721121027.23451-2-johannes.thumshirn@wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200721121027.23451-2-johannes.thumshirn@wdc.com> X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, Jul 21, 2020 at 09:10:26PM +0900, Johannes Thumshirn wrote: > In the zoned storage model, the sectors within a zone are typically all > writeable. With the introduction of the Zoned Namespace (ZNS) Command > Set in the NVM Express organization, the model was extended to have a > specific writeable capacity. > > This zone capacity can be less than the overall zone size for a NVMe ZNS > device or null_blk in zoned-mode. For other ZBC/ZAC devices the zone > capacity is always equal to the zone size. > > Use the zone capacity field instead from blk_zone for determining the > maximum inode size and inode blocks in zonefs. > > Signed-off-by: Johannes Thumshirn Looks good, Reviewed-by: Christoph Hellwig