From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] zonefs: add zone-capacity support
Date: Tue, 21 Jul 2020 17:11:28 +0100 [thread overview]
Message-ID: <20200721161128.GA24880@infradead.org> (raw)
In-Reply-To: <20200721121027.23451-2-johannes.thumshirn@wdc.com>
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 <johannes.thumshirn@wdc.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-07-21 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 12:10 [PATCH v4 0/2] zonefs: add support zone capacity support Johannes Thumshirn
2020-07-21 12:10 ` [PATCH v4 1/2] zonefs: add zone-capacity support Johannes Thumshirn
2020-07-21 16:11 ` Christoph Hellwig [this message]
2020-07-21 12:10 ` [PATCH v4 2/2] zonefs: update documentation to reflect zone size vs capacity Johannes Thumshirn
2020-07-21 16:11 ` Christoph Hellwig
2020-07-22 8:07 ` [PATCH v4 0/2] zonefs: add support zone capacity support Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200721161128.GA24880@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).