From: Edward Shishkin <edward@namesys.com>
To: siddharth kothari <sidkot@yahoo.com>
Cc: reiserfs-list@namesys.com
Subject: Re: how to linking and traversing the inmemory tree
Date: Mon, 14 Mar 2005 14:04:08 +0300 [thread overview]
Message-ID: <42356FA8.20904@namesys.com> (raw)
In-Reply-To: <20050313065817.13797.qmail@web30405.mail.mud.yahoo.com>
siddharth kothari wrote:
Hello
>hi.
>i am trying to create an in-memory for Reiser4. from
>the code i understand the following:
>1) Znode is the inmemory representation of the actual
>node.
>2) children have pointers to thier parents and alsso
>maintain their position in parents.
>3) Znodes also have the de-limiting keys
>and other fields.
>
>now my questions are:
>
>1) from where do you start traversing the tree?
>
>
From root znode if the node of current position is unknown or got
changed (there is so-called 'seal technique' to understand this),
otherwise traversing is resolved just to per-node lookup.
>2) are these nodes actually linked in memory as they
>are in a tree.
>
>
Yes, all the relations are the same
>3) once you get a key for a file how do u locate the
>lock where the data for that file is to be found.
>
>
This is a business of main search procedure (see coord_by_key())
>you obviously compare with the de-limiting keys to get
>to the node then wat.... how do u reach any other
>level since there are no down pointers.
>
>regards,
>siddharth
>
>When I was small I thought everything was either
>Black or White,
>Good or Bad,
>But I grew up to find out everthing was just Grey....
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Small Business - Try our new resources site!
>http://smallbusiness.yahoo.com/resources/
>
>
>
>
prev parent reply other threads:[~2005-03-14 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 6:58 how to linking and traversing the inmemory tree siddharth kothari
2005-03-14 11:04 ` Edward Shishkin [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=42356FA8.20904@namesys.com \
--to=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sidkot@yahoo.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 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.