On 07/14/2017 12:44 PM, Allison Henderson wrote:
> 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.
If you're forward-porting that 17-patch set from Mark, I'd suggest first reading Dave's
response to it - IIRC it amounted to a firm NAK. it also highlights the complexity
of this undertaking, and may explain why nobody has gotten it done (yet) :)
-Eric
> 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@xxxxxxxxxxxxxxx
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
