linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: Kazuya Mio <k-mio@sx.jp.nec.com>
Cc: linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: [PATCH 1/3] e4defrag: output blocks per extent by -c option
Date: Wed, 30 Sep 2009 14:28:12 -0400	[thread overview]
Message-ID: <87f94c370909301128w4bfe6f4bh80bf3d6540ed83d3@mail.gmail.com> (raw)
In-Reply-To: <4AC306B0.9070308@sx.jp.nec.com>

2009/9/30 Kazuya Mio <k-mio@sx.jp.nec.com>:
> e4defrag with -c option outputs "ratio" that means the levels of
> fragmentation. However, it's difficult for users to understand, so we will
> use blocks per extent instead of ratio.
>
> Before:
> # e4defrag -c /mnt/mp1/file
> <File>                                         now/best          ratio
> /mnt/mp1/file                                   14/1             0.01%
>
>  Total/best extents                             14/1
>  Fragmentation ratio                            0.01%
>  Fragmentation score                            0.10
>  [0-30 no problem: 31-55 a little bit fragmented: 55- needs defrag]
>  This file(/mnt/mp1/file) does not need defragmentation.
>  Done.
>
> After:
> # e4defrag -c /mnt/mp1/file
> <File>                                         now/best        blk/ext
> /mnt/mp1/file                                   14/1              7142
>
>  Total/best extents                             14/1
>  Average blocks per extent                      7142
>  Fragmentation score                            0
>  [0-30 no problem: 31-55 a little bit fragmented: 55- needs defrag]
>  This file(/mnt/mp1/file) does not need defragmentation.
>  Done.

RFC

If we are going go that far (which I like), how about adding the avg
extent size in bytes.  (ie. 7142 * blocksize I assume).

Also a note about the max blocks / extent might be good.

ie. Add a more or less hard coded line
Ext4 max blocks per extent     32,768  (128MiB)

Otherwise your typical user won't know what perfect is.

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

  reply	other threads:[~2009-09-30 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  7:20 [PATCH 1/3] e4defrag: output blocks per extent by -c option Kazuya Mio
2009-09-30 18:28 ` Greg Freemyer [this message]
2009-10-01  8:15   ` Kazuya Mio
2009-10-02 15:28     ` Greg Freemyer
2009-10-06  5:27       ` Kazuya Mio
2009-10-06 18:24         ` Greg Freemyer

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=87f94c370909301128w4bfe6f4bh80bf3d6540ed83d3@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=k-mio@sx.jp.nec.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).