From: Paul Jones <paul@pauljones.id.au>
To: Eric Levy <contact@ericlevy.name>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: RE: "hardware-assisted zeroing"
Date: Wed, 5 Jan 2022 01:12:01 +0000 [thread overview]
Message-ID: <SYXPR01MB1918E2947F617AE6436C3E9E9E4B9@SYXPR01MB1918.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <ca2d0ec03b6ec81add904d44e432ec063777b6e0.camel@ericlevy.name>
> -----Original Message-----
> From: Eric Levy <contact@ericlevy.name>
> Sent: Wednesday, 5 January 2022 11:44 AM
> To: linux-btrfs@vger.kernel.org
> Subject: Re: "hardware-assisted zeroing"
>
> 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?
Yes, but in an ssd it will get remapped (in hardware) as part of the wear-leveling algorithm, otherwise the front part will wear faster than the rear, assuming free space is allocated from the front.
next prev parent reply other threads:[~2022-01-05 1:12 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 [this message]
2022-01-05 1:20 ` Eric Levy
2022-01-05 1:21 ` Zygo Blaxell
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=SYXPR01MB1918E2947F617AE6436C3E9E9E4B9@SYXPR01MB1918.ausprd01.prod.outlook.com \
--to=paul@pauljones.id.au \
--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.