From: Andreas Dilger <adilger@dilger.ca>
To: Ts'o Theodore <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: ext4-lazy (SMR-optimizations) landing to kernel?
Date: Mon, 10 Apr 2017 21:06:23 -0600 [thread overview]
Message-ID: <6B0F0C59-6930-41B3-8EE4-EA5BEECEB9F9@dilger.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi Ted,
now that FAST'17 is behind us, is there any plan to land the ext4-lazy code
(SMR optimizations) to the upstream kernel? This looks like it improves
some workloads even without SMR disks, and doesn't have any noticeable
overhead for other workloads.
I'd guess the one thing that we might want to do is still allow the journal
to optionally checkpoint the metadata to the filesystem in the background,
when the filesystem is otherwise idle, so that in case of journal loss for
some reason the whole filesystem is not lost?
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2017-04-11 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 3:06 Andreas Dilger [this message]
2017-04-11 3:23 ` ext4-lazy (SMR-optimizations) landing to kernel? Darrick J. Wong
2017-04-17 14:18 ` Eric Sandeen
2017-04-17 19:59 ` Andreas Dilger
2017-04-18 3:28 ` Theodore Ts'o
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=6B0F0C59-6930-41B3-8EE4-EA5BEECEB9F9@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).