linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andreas@rid-net.de
To: linux-ext4@vger.kernel.org
Subject: defragmentation of boot related files
Date: Wed, 25 Aug 2010 14:00:03 +0200	[thread overview]
Message-ID: <4C7505C3.1070509@rid-net.de> (raw)

hi,

I try to find ways to reduce the start time of programs or the whole 
operating system. The idea to increase disk performance is to gather all 
related files on disk physically close together. Unlike the last patches 
from Kazuya Mio for "relevant file defragmentation" files used by system 
boot are mostly not in the same directory.

First i look at the EXT4_IOC_MOVE_EXT call.
To reduce the amount of disk seeks i want to move the extents from 
several files into a single donor file. To do so i increment the 
move_extent.donor_start by the size of each file. But i got an error.

The error is caused by the lines in the kernel source 
fs/ext4/move_extent.c:998
998	/* Start offset should be same */
999	if (orig_start != donor_start) {
1000		ext4_debug("ext4 move extent: orig and donor's start "
1001		     "offset are not same [ino:orig %lu, donor %lu]\n",
1002                 orig_inode->i_ino, donor_inode->i_ino);
1003            return -EINVAL;
1004    }

Is there a reason why the offset of the original file and the donor file 
must be the same?

As i can see the patch for relevant file defragmentation in e4defrag 
supports only directories. May it be possible to select any desired file?

What would you suggest as the best way to put files physically together?

If I could help, tell me. :)

Regards,

andy

             reply	other threads:[~2010-08-25 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 12:00 andreas [this message]
2010-08-26  8:50 ` defragmentation of boot related files Kazuya Mio
2010-08-26 18:10   ` Greg Freemyer
2010-08-26 20:16     ` andreas
2010-08-27  0:47       ` Andreas Dilger
2010-08-27 11:21       ` Kazuya Mio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C7505C3.1070509@rid-net.de \
    --to=andreas@rid-net.de \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).