From: Christoph Hellwig <hch@infradead.org>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: xfs@oss.sgi.com
Subject: Re: inode parent pointer attributes
Date: Fri, 23 Apr 2010 09:00:51 -0400 [thread overview]
Message-ID: <20100423130051.GA7163@infradead.org> (raw)
In-Reply-To: <8A91C8CC-6DC4-4334-A2B9-ED814DAF0352@filmlight.ltd.uk>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Fri, Apr 23, 2010 at 12:07:08PM +0100, Roger Willcocks wrote:
> Hi folks,
>
> Commit 6d73cf133c5477f7038577bfeda603ce9946f8cb reintroduced the
> XFS_SB_VERSION2_PARENTBIT in the kernel headers, which is described
> in the xfs filesystem structure document as 'All inodes must have an
> extended attribute that points back to its parent inode'.
>
> There's currently (afaict) no Linux kernel implementation of this. But
> it's something I would find very useful for a filesystem extension I'm
> working on.
Work on the Linux port of this feature stopped when SGI closed the
Melbourne engineering office where people were working on it.
Fortunately SGI did publish the latest development state of it for
others to continue. I've attached my local copy in case you're
interested on finishing this.
[-- Attachment #2: parent_pointers.tar.gz --]
[-- Type: application/x-gzip, Size: 15274 bytes --]
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-23 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:07 inode parent pointer attributes Roger Willcocks
2010-04-23 13:00 ` Christoph Hellwig [this message]
2010-04-23 14:50 ` Roger Willcocks
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=20100423130051.GA7163@infradead.org \
--to=hch@infradead.org \
--cc=roger@filmlight.ltd.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox