linux-ext4 - ext4-lazy (SMR-optimizations) landing to kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <6B0F0C59-6930-41B3-8EE4-EA5BEECEB9F9@dilger.ca>
Date:   Mon, 10 Apr 2017 21:06:23 -0600
From:   Andreas Dilger <adilger@...ger.ca>
To:     Ts'o Theodore <tytso@....edu>
Cc:     linux-ext4 <linux-ext4@...r.kernel.org>
Subject: ext4-lazy (SMR-optimizations) landing to kernel?

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

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)