From: Allison Henderson <allison.henderson@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>,
cmaiolino@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: Parent pointers
Date: Fri, 14 Jul 2017 10:44:39 -0700 [thread overview]
Message-ID: <59690307.9090407@oracle.com> (raw)
In-Reply-To: <817aafad-6b64-3700-6752-c63d7e5cdde7@sandeen.net>
On 7/14/2017 7:04 AM, Eric Sandeen wrote:
>
>
> On 07/14/2017 03:50 AM, Carlos Maiolino wrote:
>> Hi,
>>
>> On Thu, Jul 13, 2017 at 04:25:25PM -0700, Allison Henderson wrote:
>>> Hi all,
>>>
>>> I've been doing some digging on adding parent pointers to xfs and wanted to
>>> send a note to folks here to get peoples opinions on it.
>>
>> Are you talking about parent pointers in the BTrees?
>>
>
> No, see [RFC 00/17] RFC parent inode pointers. for example, from long
> ago.
>
> "Parent inode support allow XFS to quickly derive a file name and
> path from the mount point. This can aid in directory/path policies
> and can help relocate items during filesystem shrink."
>
> It has a long and ... difficult history.
>
> -Eric
Right, so to expand on Eric's answer, it looks like Dave and Brian had
been working on some improvements based on that set, but it's not quite
finished yet. The idea is that we add an extended attribute to keep
track of the parents inode and generation, and also the child entries
offset, and filename. So in this solution the EA is name={parent inode
#, parent inode generation, dirent offset}, value={dirent filename}.
My goal at the moment is just to get it compiling again and finish out
some of the sub routines that maintain it. It looks like it hasn't had
much attention in a while, so I wanted to let people know the direction
I'm planning to move in before I get too far in.
Allison
>
>>> I got in touch
>>> with Brian Foster not too long ago and he had some code partially done from
>>> about a year or so ago (looks like it has patches from Dave Chinner and Mark
>>> Tinguely as well). So I am hoping to be able to use what we have so far to
>>> create something updated and finished out. I am still pretty new to the xfs
>>> code, so at the moment I am still just going through old discussion threads,
>>> and reviewing the patches. But for the most part I just wanted to see what
>>> people thought and get everyone on board with the idea. Suggestions and
>>> feedback are much appreciated. Thank you!!
>>>
>>
>> It will be better if you can describe in more details if you have any specific
>> goal with this, and/or what kind of improvement you expect to have with it,
>> adding something new without a reason, is usually not well received.
>>
>> Cheers
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-07-14 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 23:25 Parent pointers Allison Henderson
2017-07-14 8:50 ` Carlos Maiolino
2017-07-14 14:04 ` Eric Sandeen
2017-07-14 17:44 ` Allison Henderson [this message]
2017-07-14 18:46 ` Eric Sandeen
2017-07-14 19:07 ` Brian Foster
2017-07-14 19:14 ` Eric Sandeen
2017-07-14 22:46 ` Darrick J. Wong
2017-07-15 16:36 ` Tinguely, Mark
2017-07-17 14:49 ` Brian Foster
2017-07-17 15:33 ` Mark Tinguely
2017-07-17 22:53 ` Darrick J. Wong
2017-07-17 14:48 ` Brian Foster
2017-07-17 22:14 ` Dave Chinner
2017-07-17 23:10 ` Darrick J. Wong
2017-07-18 0:10 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2017-07-14 4:54 Allison Henderson
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=59690307.9090407@oracle.com \
--to=allison.henderson@oracle.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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