From: "hch@infradead.org" <hch@infradead.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] block: all zones zone management operations
Date: Thu, 26 Mar 2020 02:30:49 -0700 [thread overview]
Message-ID: <20200326093049.GB6478@infradead.org> (raw)
In-Reply-To: <CO2PR04MB23433C37660B9A8B53D95790E7CF0@CO2PR04MB2343.namprd04.prod.outlook.com>
On Thu, Mar 26, 2020 at 08:23:34AM +0000, Damien Le Moal wrote:
> Open & Close all zones are indeed not super useful, at least on SMR drives. But
> finishing all zones does have some benefit, namely the ability to quickly change
> all incompletely written zones into "read-only" full zones. For drives with low
> zone resources (open or active zones), this can be useful to recover zone
> resources. Again, not so much on SMR drives, but this could come in handy for
> ZNS drives with low zone resources (max open zones etc).
What quantifies the "some benefit"? If you have an application that
micro-manages the zone state it better knows what zones are open. But
even if we want to add a finish all I'd rather wait for ZNS support
to land and real use cases, as it sounds all rather dubious.
next prev parent reply other threads:[~2020-03-26 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 4:30 [PATCH] block: all zones zone management operations Damien Le Moal
2020-03-26 7:28 ` Christoph Hellwig
2020-03-26 8:23 ` Damien Le Moal
2020-03-26 9:30 ` hch [this message]
2020-03-28 8:13 ` Damien Le Moal
2020-03-28 8:22 ` hch
2020-03-28 8:27 ` Damien Le Moal
2020-03-28 8:31 ` hch
2020-03-28 8:37 ` 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=20200326093049.GB6478@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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