[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87f94c370909301128w4bfe6f4bh80bf3d6540ed83d3@mail.gmail.com>
Date: Wed, 30 Sep 2009 14:28:12 -0400
From: Greg Freemyer <greg.freemyer@...il.com>
To: Kazuya Mio <k-mio@...jp.nec.com>
Cc: linux-ext4@...r.kernel.org, Theodore Tso <tytso@....edu>
Subject: Re: [PATCH 1/3] e4defrag: output blocks per extent by -c option
2009/9/30 Kazuya Mio <k-mio@...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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists