From: Vlad Apostolov <vapo@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
Timothy Shimmin <tes@sgi.com>, Barry Naujok <bnaujok@sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: REVIEW: xfs_reno #2
Date: Tue, 20 Nov 2007 09:08:12 +1100 [thread overview]
Message-ID: <4742094C.2020705@sgi.com> (raw)
In-Reply-To: <4741B14D.8020004@sandeen.net>
Eric Sandeen wrote:
> Christoph Hellwig wrote:
>
>> On Fri, Nov 16, 2007 at 05:20:28PM +1100, Timothy Shimmin wrote:
>>
>>> 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.
>>>
>> What parent pointers?
>>
>>
>>
>
> The ones not yet released I guess :)
>
It is a released and existing feature on XFS for Irix, that we are back
porting to
Linux. You will see some patches soon.
Regards,
Vlad
>
>>> Vlad Apostolov wrote:
>>>
>>>> When the XFS parent pointers feature is released...
>>>>
>
> -Eric
>
next prev parent reply other threads:[~2007-11-19 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 4:25 REVIEW: xfs_reno #2 Barry Naujok
2007-10-17 15:48 ` Ruben Porras
2007-11-16 6:04 ` Vlad Apostolov
2007-11-16 6:20 ` Timothy Shimmin
2007-11-18 23:13 ` Vlad Apostolov
2007-11-18 23:19 ` Vlad Apostolov
2007-11-19 12:39 ` Christoph Hellwig
2007-11-19 15:52 ` Eric Sandeen
2007-11-19 22:08 ` Vlad Apostolov [this message]
2007-11-19 3:48 ` Lachlan McIlroy
2007-11-20 1:36 ` David Chinner
2007-11-23 14:30 ` Ruben Porras
2008-03-06 16:11 ` Ruben Porras
2008-03-06 16:10 ` Ruben Porras
2008-06-03 20:34 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4742094C.2020705@sgi.com \
--to=vapo@sgi.com \
--cc=bnaujok@sgi.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.