From: Oleg Drokin <green@namesys.com>
To: Phil Howard <phil-reiserfs@ipal.net>
Cc: Yura Umanets <umanets@priocom.com>, reiserfs-list@namesys.com
Subject: Re: using reiserfs as a DB
Date: Tue, 23 Apr 2002 10:46:41 +0400 [thread overview]
Message-ID: <20020423104641.B2930@namesys.com> (raw)
In-Reply-To: <20020422231645.GD8407@vega.ipal.net>
Hello!
On Mon, Apr 22, 2002 at 06:16:45PM -0500, Phil Howard wrote:
> | The first component is identifier of directory where given object (file
> | or directory) lies. Second - identifier of the given object. Third
> | component - offset inside object. If object is file, then offset is
> | offset inside this file, if directory - hashed name of first entry in
> | this direntry. And finally last component is type of the item (statdata,
> | direntry, direct item, indirect item).
> How is the application going to know what the key is for a particular
> file? How is the application going to translate what it has as a key,
It seems I used wrong word. What was used to acces files were in fact
md5 sums of their names (the URL in squid case).
> into the kind of key the raw interface uses? How costly is this lookup?
Once Nikita will appear, he can explain better because he invented the code,
I believe.
Bye,
Oleg
next prev parent reply other threads:[~2002-04-23 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 20:53 using reiserfs as a DB Phil Howard
2002-04-22 13:20 ` Oleg Drokin
2002-04-22 13:47 ` Hans Reiser
2002-04-22 14:03 ` Nikita Danilov
2002-04-22 17:44 ` Phil Howard
2002-04-22 18:12 ` Yura Umanets
2002-04-22 19:26 ` Richard Emslie
2002-04-23 6:44 ` Oleg Drokin
2002-04-22 23:16 ` Phil Howard
2002-04-23 6:46 ` Oleg Drokin [this message]
2002-04-23 8:50 ` Nikita Danilov
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=20020423104641.B2930@namesys.com \
--to=green@namesys.com \
--cc=phil-reiserfs@ipal.net \
--cc=reiserfs-list@namesys.com \
--cc=umanets@priocom.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.