| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: Review: factor extracting extent size hints from the inode |
| From: | Nathan Scott <nscott@xxxxxxxxxx> |
| Date: | Tue, 12 Jun 2007 16:39:46 +1000 |
| Cc: | Vlad Apostolov <vapo@xxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20070612060800.GP86004887@xxxxxxx> |
| Organization: | Aconex |
| References: | <20070604052333.GR85884050@xxxxxxx> <466E2B76.7010707@xxxxxxx> <20070612060800.GP86004887@xxxxxxx> |
| Reply-to: | nscott@xxxxxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On Tue, 2007-06-12 at 16:08 +1000, David Chinner wrote: > > If you use this method of setting the extent size hint, then you will > *always* get the XFS_DIFLAG_EXTSIZE flag set when you have an extent > size hint, regardless of whether it is a realtime file or not. The extsize flag is relatively recent though, and traditionally realtime files could have had their extsize explicitly set with no associated extsize flag (thats just how it was implemented, originally, in realtime). But, not many people use realtime, even fewer would be using the extent size option with realtime (like, none?, on Linux anyway) ... so, you could pretty much make whatever rule you like. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd, David Chinner |
|---|---|
| Next by Date: | Re: [PATCH 1/5] fallocate() implementation in i86, x86_64 and powerpc, Amit K. Arora |
| Previous by Thread: | Re: Review: factor extracting extent size hints from the inode, David Chinner |
| Next by Thread: | Re: Review: factor extracting extent size hints from the inode, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |