From: Peter Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Doubly indexed tree / changelogs
Date: Wed, 24 Sep 2008 10:50:51 +0800 [thread overview]
Message-ID: <C4FFCC0B.7DC3%peter.braam@sun.com> (raw)
In-Reply-To: <18648.40197.532872.168033@gargle.gargle.HOWL>
The idea is ok, but scale may turn out to be different than expected.
There could be a huge amount of filesets containing the word "Bin Laden",
say 100,000 of them.
Would two directories work?
Peter
On 9/23/08 3:38 PM, "Nikita Danilov" <Nikita.Danilov@Sun.COM> wrote:
> Peter Braam writes:
>> Hi Nikita, Nathan -
>>
>> After some pondering I have come to two conclusions.
>>
>> To encode filesets, we need a tree that makes two iterations fast:
>>
>> 1. list all filesets that contain a certain object
>> 2. list all objects in a certain fileset
>>
>> Is there a doubly indexed tree for this?
>
> I don't know of a data-structure that provides ready solution for this.
> As Alex pointed out k-d-trees do not fit there (they effectively use a
> key composed of the alternating sequences of bits of the original keys),
> and `geographical trees' that data bases use to store 2-d data use very
> special notion of proximity.
>
> But, thinking about a fileset as a generalized directory, isn't this the
> same problem as `list all files in directory' and `find all parent
> directories of a file'? It probably makes sense to use the same
> mechanism to deal with directories and filesets.
>
> Our current solution is to use EA to keep track of all parent
> directories, do you see any problems with applying it to filesets?
>
>>
>> Peter
>
> Nikita.
prev parent reply other threads:[~2008-09-24 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 23:40 [Lustre-devel] Doubly indexed tree / changelogs Peter Braam
2008-09-22 5:52 ` Alex Zhuravlev
2008-09-22 6:58 ` Peter Braam
2008-09-22 7:05 ` Alex Zhuravlev
2008-09-22 7:13 ` Peter Braam
2008-09-22 7:26 ` Alex Zhuravlev
2008-09-23 3:49 ` Nathaniel Rutman
2008-09-23 9:20 ` Peter Braam
2008-09-23 21:46 ` Nathaniel Rutman
2008-09-23 22:48 ` Peter Braam
2008-09-23 7:38 ` Nikita Danilov
2008-09-24 2:50 ` Peter Braam [this message]
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=C4FFCC0B.7DC3%peter.braam@sun.com \
--to=peter.braam@sun.com \
--cc=lustre-devel@lists.lustre.org \
/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.