linux-ext4 - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170411032334.GA5066@birch.djwong.org>
Date:   Mon, 10 Apr 2017 20:23:34 -0700
From:   "Darrick J. Wong" <darrick.wong@...cle.com>
To:     Andreas Dilger <adilger@...ger.ca>
Cc:     "Ts'o Theodore" <tytso@....edu>,
        linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: ext4-lazy (SMR-optimizations) landing to kernel?

On Mon, Apr 10, 2017 at 09:06:23PM -0600, Andreas Dilger wrote:
> 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?

Don't forget to fix jbd2_bh_submit_read to behave when JBD2_FLAG_ESCAPE
is set on a journal data block.

--D

> 
> Cheers, Andreas
> 
> 
> 
> 
>