| To: | Vlad Apostolov <vapo@xxxxxxx> |
|---|---|
| Subject: | Re: REVIEW: xfs_reno #2 |
| From: | Timothy Shimmin <tes@xxxxxxx> |
| Date: | Fri, 16 Nov 2007 17:20:28 +1100 |
| Cc: | Barry Naujok <bnaujok@xxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, xfs-dev <xfs-dev@xxxxxxx> |
| In-reply-to: | <473D32D9.2020500@xxxxxxx> |
| References: | <op.tznnweh23jf8g2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <473D32D9.2020500@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.6 (Macintosh/20070728) |
Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directory. This may not be that easy though. Really? Apart from the swapping of extents, reno uses standard calls doesn't it, in which case any movement of inodes will have the parent pointers updated by the normal vnode ops (e.g. mkdir, rename) in the kernel. --Tim |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [xfs-masters] [PATCH] remove BPCSHIFT and NB?P? macros - was fs/xfs: remove duplicated defines, Lachlan McIlroy |
|---|---|
| Next by Date: | Re: [PATCH, RFC] Move AIL pushing into a separate thread, Christoph Hellwig |
| Previous by Thread: | Re: REVIEW: xfs_reno #2, Vlad Apostolov |
| Next by Thread: | Re: REVIEW: xfs_reno #2, Vlad Apostolov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |