linux-ext4 - Re: defrag deployment status (was Re: [PATCH] ext4: allow defrag (EXT4_IOC_MOVE

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]

Date:	Mon, 8 Mar 2010 17:00:57 +0100
From:	Christian Borntraeger <borntraeger@...ibm.com>
To:	David Newall <davidn@...idnewall.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-ext4@...r.kernel.org,
	linux-kernel@...r.kernel.org, Akira Fujita <a-fujita@...jp.nec.com>
Subject: Re: defrag deployment status (was Re: [PATCH] ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode)

Am Montag 08 März 2010 16:33:46 schrieb David Newall:
> Christian Borntraeger wrote:
> > Some bigger things are missing in the e4defrag tool:
> > ...
> > - overall layout considerations (e.g. putting files close to its directory or
> >   use the atime to move often used files to the beginning of a disk etc.)
> 
> Shouldn't oft-used files be placed closer to the middle?  If you place 
> them at the beginning of the file, it's only possible for the head-stack 
> to be close to the file from the inner direction.  Place them in the 
> middle and it's possible for the head-stack to be close from the outer 
> direction, too, which sounds like a doubling of probability.  It seems 
> that it's the least frequently used files that should be placed at one 
> end of the disk or the other.
> 

Maybe. This was just an example of things that you can come
up with and which are not yet possible up in e4defrag. 

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