From: Timothy Shimmin <tes@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: Johan Andersson <johan@e-626.net>,
xfs@oss.sgi.com, Nathan Scott <nscott@aconex.com>
Subject: Re: xfs_fsr allocation group optimization
Date: Fri, 15 Jun 2007 17:20:36 +1000 [thread overview]
Message-ID: <46723DC4.1080107@sgi.com> (raw)
In-Reply-To: <20070612014452.GK86004887@sgi.com>
David Chinner wrote:
> On Mon, Jun 11, 2007 at 08:51:32AM +0200, Johan Andersson wrote:
>> Does anyone know of a good way to find one filename that points o a
>> certain inode?
>
> We need an rmap....
>
> We have some prototype linux code that does parent pointers (i.e.
> each inode has a back pointer to it's parent inode), but that, IIUC,
> is a long way from prime-time. Tim?
>
> Cheers,
>
> Dave.
I don't know about a "long way" (longer to fully supported, yes)
Firstly, I need to move its hooks out of linux-2.6/xfs_iops.c which were
referring to xfs inodes (instead of vnodes) probably back where they were in
xfs_vnodeops.c.
Nathan, did you have some other suggestion than this - unfortunately,
I haven't looked at this code (until recently) for a while.
Cheers,
Tim.
next prev parent reply other threads:[~2007-06-15 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 6:51 xfs_fsr allocation group optimization Johan Andersson
2007-06-11 7:35 ` Chris Wedgwood
2007-06-11 8:43 ` Johan Andersson
2007-06-11 9:01 ` Chris Wedgwood
2007-06-11 9:15 ` Johan Andersson
2007-06-11 9:41 ` Chris Wedgwood
2007-06-11 10:39 ` Johan Andersson
2007-06-11 15:58 ` Chris Wedgwood
2007-06-11 23:07 ` Nathan Scott
2007-06-12 1:38 ` David Chinner
2007-06-12 1:41 ` David Chinner
2007-06-12 1:44 ` David Chinner
2007-06-15 7:20 ` Timothy Shimmin [this message]
2007-06-15 7:24 ` Nathan Scott
2007-06-15 7:40 ` Johan Andersson
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=46723DC4.1080107@sgi.com \
--to=tes@sgi.com \
--cc=dgc@sgi.com \
--cc=johan@e-626.net \
--cc=nscott@aconex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox