| To: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH 5/5] xfs: increase inode cluster size for v5 filesystems |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 14 Nov 2013 12:51:52 -0600 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1383280040-21979-6-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1383280040-21979-1-git-send-email-david@xxxxxxxxxxxxx> <1383280040-21979-6-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 10/31/13, 11:27 PM, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > v5 filesystems use 512 byte inodes as a minimum, so read inodes in > clusters that are effectively half the size of a v4 filesystem with > 256 byte inodes. For v5 fielsystems, scale the inode cluster size > with the size of the inode so that we keep a constant 32 inodes per > cluster ratio for all inode IO. Ok, I'm happy with this now that I was reminded of the difference between clusters & chunks. :/ Ben, regarding your compat concern, I agree w/ Dave that there should be no failures moving forward or back; as he & I mentioned (I had missed his other reply), the kernel already (used to) set different cluster sizes based on the memory available in the machine that mounted the filesystem. So: Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] update xfs maintainers, Alex Elder |
|---|---|
| Next by Date: | Re: [PATCH] xfstests: stop special casing nfs and udf, Eric Sandeen |
| Previous by Thread: | Re: [PATCH 5/5] xfs: increase inode cluster size for v5 filesystems, Eric Sandeen |
| Next by Thread: | [PATCH] xfs: fix unlock in xfs_bmap_add_attrfork, Mark Tinguely |
| Indexes: | [Date] [Thread] [Top] [All Lists] |