From: antlists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "Amount" of fstrim? (curiosity driven, no paranoia :)
Date: Mon, 27 Apr 2020 20:07:04 +0100 [thread overview]
Message-ID: <be39f3d8-5ac8-40b0-0527-898714a6e097@youngman.org.uk> (raw)
In-Reply-To: <CAGfcS_mB-hgK+A9wzQKmZA9OaT-A+L=RH7kFoXQMS7KqEVSn1g@mail.gmail.com>
On 27/04/2020 17:59, Rich Freeman wrote:
> Really though a better solution than any of this is for the filesystem
> to be more SSD-aware and just only perform writes on entire erase
> regions at one time. If the drive is told to write blocks 1-32 then
> it can just blindly erase their contents first because it knows
> everything there is getting overwritten anyway. Likewise a filesystem
> could do its own wear-leveling also, especially on something like
> flash where the cost of fragmentation is not high. I'm not sure how
> well either zfs or ext4 perform in these roles. Obviously a solution
> like f2fs designed for flash storage is going to excel here.
The problem here is "how big is an erase region". I've heard comments
that it is several megs. Trying to consolidate writes into megabyte
blocks is going to be tricky, to say the least, unless you're dealing
with video files or hi-res photos - I think the files my camera chucks
out are in the 10MB region ... (24MP raw...)
Cheers,
Wol
next prev parent reply other threads:[~2020-04-27 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 14:52 [gentoo-user] "Amount" of fstrim? (curiosity driven, no paranoia :) tuxic
2020-04-26 15:20 ` Rich Freeman
2020-04-26 16:15 ` tuxic
2020-04-26 19:29 ` Rich Freeman
2020-04-27 1:43 ` tuxic
2020-04-27 1:58 ` Rich Freeman
2020-04-27 3:14 ` tuxic
2020-04-27 8:22 ` William Kenworthy
2020-04-27 10:32 ` Alan Mackenzie
2020-04-27 15:12 ` Kent Fredric
2020-04-27 16:20 ` tuxic
2020-04-27 16:59 ` Rich Freeman
2020-04-27 19:07 ` antlists [this message]
2020-04-27 19:17 ` Rich Freeman
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=be39f3d8-5ac8-40b0-0527-898714a6e097@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.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