linux-ext4 - Re: Large File Deletion Comparison (ext3, ext4, XFS)

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] [day] [month] [year] [list]

Message-ID: <4632619E.4080208@clusterfs.com>
Date:	Sat, 28 Apr 2007 00:48:30 +0400
From:	Alex Tomas <alex@...sterfs.com>
To:	Andreas Dilger <adilger@...sterfs.com>
CC:	Valerie Clement <valerie.clement@...l.net>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: Large File Deletion Comparison (ext3, ext4, XFS)

Andreas Dilger wrote:
> Ah, one thing that is only mentioned in the URL is that the "IO count" is
> in units of 512-byte sectors.  In the case of XFS doing logical journaling
> this avoids a huge amount of double writes to the journal and then to the
> filesystem.  I still think ext4 could do better than it currently does.

I thought about this in context of huge directories when working set of blocks
is very large and it doesn't fit journal causing frequent commits. two ideas
I was thinking of are: 1) journal "change" where possible 2) compress whole
transaction to be written in the journal

thanks, Alex


-
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