linux-ext4 - Re: defragmentation of boot related files

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: <4C76CB9C.2060207@rid-net.de>
Date:	Thu, 26 Aug 2010 22:16:28 +0200
From:	andreas@...-net.de
To:	Greg Freemyer <greg.freemyer@...il.com>, k-mio@...jp.nec.com,
	linux-ext4@...r.kernel.org
Subject: Re: defragmentation of boot related files

hi,

>> Usage: e4defrag -r directory...| device...
>>        e4defrag -r base_file move_file...<--- new
>>

The new interface looks nice. As I see it's easy to implement cause only 
the main-function must be modified. If you have no objections, I will do 
it myself and send you the patch to review it.

> I suspect the original idea would work better because it is more
> likely to pack the libs / files into perfectly contiguous block
> ranges.

I don't know if it makes a difference for the block allocator. Even 
though you know the size of all files to be moved.

For a better result, may it be possible to create a base_file whose 
inode is part of an empty block group?

  Andreas
--
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