| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] xfs_db: defang frag command |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 23 May 2016 08:06:28 -0700 |
| Cc: | xfs-oss <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <2d21b9ba-6db7-e239-3be8-a7bd5e1c39cc@xxxxxxxxxxx> |
| References: | <2d21b9ba-6db7-e239-3be8-a7bd5e1c39cc@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Wed, May 11, 2016 at 02:41:28PM -0500, Eric Sandeen wrote: > Too many people freak out about this fictitious "fragmentation > factor." As shown in the fact, it is largely meaningless, because > the number approaches 100% extremely quickly for just a few > extents per file. > > I thought about removing it altogether, but perhaps a note > about its uselessness, and a more soothing metric (avg extents > per file) might be useful. Heh. Looks reasonable: Reviewed-by: Christoph Hellwig <hch@xxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2/2] linux.h: include <linux/fs.h>, Christoph Hellwig |
|---|---|
| Next by Date: | [PATCH] xfs: define XFS_IOC_FREEZE even if FIFREEZE is defined, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH] xfs_db: defang frag command, Carlos Maiolino |
| Next by Thread: | [PATCH v7 0/6] dax: handling media errors (clear-on-zero only), Vishal Verma |
| Indexes: | [Date] [Thread] [Top] [All Lists] |