All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yura Umanets" <umanets@priocom.com>
To: Phil Howard <phil-reiserfs@ipal.net>
Cc: reiserfs-list@namesys.com
Subject: Re: using reiserfs as a DB
Date: Mon, 22 Apr 2002 21:12:36 +0300	[thread overview]
Message-ID: <3CC45294.2060806@priocom.com> (raw)
In-Reply-To: 20020422174449.GC8407@vega.ipal.net

Phil Howard wrote:

> "By the keys" means what?  Are the keys the filenames/paths, 

The key in reiserfs seems like four-dimentional coordinate of the 
certain item in filesystem.

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).

Therefore it is very fast to access corresponding object item. This is 
just $tree_height blocks to be read.

> Does the raw interface simply shortcut access to files in a normal reiserfs
> mounted filesystem, which can also still be accessed the usual way, or is it
> a special object which can only be accessed that way (if so, then it loses
> the advantage of being able to use conventional tools that work on files, and
> ends up being pretty much a DB lib implemented in kernel space).  Since most
> operations would be open() file, read() file once (because nothing would be
> larger than one block), and close(), a single system call that allowed to
> just fetch the contents given a name would certainly be a plus for the server
> component.


The instance of what is a raw access to files and directories you can 
see on http://reiserfs.linux.kiev.ua/progsreiserfs-0.3.0.tar.gz in 
files: object.c, file.c, dir.c


  reply	other threads:[~2002-04-22 18:12 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 [this message]
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
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=3CC45294.2060806@priocom.com \
    --to=umanets@priocom.com \
    --cc=phil-reiserfs@ipal.net \
    --cc=reiserfs-list@namesys.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.