linux-ext4 - [LSF/FS TOPIC] Journal guided RAID resync

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: <AANLkTik72=3h4T=MNnaqLFdfYHraYp8T=eaNyijFiY9f@mail.gmail.com>
Date:	Tue, 8 Mar 2011 17:35:36 +0200
From:	Amir Goldstein <amir73il@...il.com>
To:	lsf-pc@...ts.linuxfoundation.org
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: [LSF/FS TOPIC] Journal guided RAID resync

Hi All,

I have picked up the old ext3/jbd patches a while ago and
was trying to figure out how difficult would it be to port them
to ext4/jbd2.

The gain from these patches to anyone using software RAID
should be clear, see:
http://lwn.net/Articles/363490/

What is not clear to me at this point is what are the
performance implications, if any, of withholding "declared" data
writeback until journal commit.

I also did not get to estimating the effort involved in the porting
to ext4/jbd2. The absence of ext3/jbd "dirty data" buffers list is
going to be one of the issues to deal with.

Does anyone out there have interest in pushing this forward?

Amir.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html