From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Eric Levy <contact@ericlevy.name>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: "hardware-assisted zeroing"
Date: Tue, 4 Jan 2022 20:21:58 -0500 [thread overview]
Message-ID: <YdTytv47JUGujVl5@hungrycats.org> (raw)
In-Reply-To: <ca2d0ec03b6ec81add904d44e432ec063777b6e0.camel@ericlevy.name>
On Tue, Jan 04, 2022 at 07:44:21PM -0500, Eric Levy wrote:
> On Wed, 2022-01-05 at 00:38 +0000, Paul Jones wrote:
>
> > It's also needed to keep throughput high on near full drives, as
> > flash can't write at anywhere near the rated speed of the drive. If
> > there is not enough free blocks to dump incoming data then the drive
> > needs to stop and wait for in-progress data to finish writing/erasing
> > before processing the next command.
>
> Isn't the address of a free block, for writing new data, resolved by
> the file system, based on the allocation data it maintains, not by the
> hardware?
No SSD works this way.
You say "hardware", but a SSD is an embedded computer running a minimalist
filesystem in its firmware (only one file, the nominal size of the
entire drive). SSDs can't directly map LBA addresses to physical media,
so they need to implement data placement algorithms that have noticeable
side-effects on performance.
ZNS SSD devices do address mapping entirely in reverse--in a write
command, the host says "append this block to zone Z", the drive chooses
a block address for the data within that zone, and sends the written
block address back to the host filesystem as part of the command reply.
This allows the drive to implement writes in parallel (so they are
subject to reordering) without having to store where it put user data
in the SSD's own memory.
next prev parent reply other threads:[~2022-01-05 1:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 11:08 "hardware-assisted zeroing" Eric Levy
2022-01-03 11:17 ` Qu Wenruo
2022-01-03 11:24 ` Eric Levy
2022-01-03 11:51 ` Qu Wenruo
2022-01-04 10:50 ` Eric Levy
2022-01-04 20:49 ` Zygo Blaxell
2022-01-04 22:37 ` Eric Levy
2022-01-04 22:46 ` Qu Wenruo
2022-01-05 0:38 ` Paul Jones
2022-01-05 0:44 ` Eric Levy
2022-01-05 1:12 ` Paul Jones
2022-01-05 1:20 ` Eric Levy
2022-01-05 1:21 ` Zygo Blaxell [this message]
2022-01-05 1:26 ` Eric Levy
2022-01-05 1:33 ` Zygo Blaxell
2022-01-05 1:37 ` Eric Levy
2022-01-05 2:20 ` Zygo Blaxell
2022-01-05 1:32 ` Zygo Blaxell
2022-01-04 22:37 ` Qu Wenruo
2022-01-03 11:46 ` David Disseldorp
2022-01-03 11:57 ` Qu Wenruo
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=YdTytv47JUGujVl5@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=contact@ericlevy.name \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.