All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Sanchez Acosta <asanchez@gnome.org>
To: reiserfs-list@namesys.com
Subject: Some more basic questions.
Date: 10 Nov 2003 05:15:20 +0100	[thread overview]
Message-ID: <1068437719.3362.24.camel@voyager> (raw)

Hello,

I don't understand so well how the dancing trees work. I've seen in the
documentation that are faster than B+ trees, but I don't understand the
reason. Somebody can explain me how does it work a dancing tree and
where does reiserfs use it?

Other thing that I don't understand is the cache design, where are used
caches in the filesystem? 

And why is better to use extents than BLOBs? A lot of databases use
BLOB's to storage the data and get good performance with.

What security features provide reiser4? I have seen that you can use
crypto support and crypto compressing, does it support other security
features? does it use the new CryptoAPI? 

And other thing, if I want to do a new plugin, what I have to do? Any
documentation related?

Thanks in advance.
-- 
Alejandro Sanchez Acosta <asanchez@gnome.org>


             reply	other threads:[~2003-11-10  4:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10  4:15 Alejandro Sanchez Acosta [this message]
2003-11-10 12:17 ` Some more basic questions Alex Zarochentsev
  -- strict thread matches above, loose matches on Subject: below --
2014-05-28 20:59 Marcus White
2014-05-29  6:04 ` Venkateswara Rao Nandigam
2014-05-29  6:45 ` Zhang Haoyu
2014-05-30  4:06   ` Marcus White
2014-05-30  6:48     ` Zhang Haoyu
2014-06-02 21:19       ` Marcus White
2014-06-03  3:43         ` Zhang Haoyu
2014-06-03  4:53           ` Marcus White
2014-06-03  6:47             ` Zhang Haoyu
2014-06-03  6:54         ` Venkateswara Rao Nandigam
2014-06-03 11:00         ` Zhang Haoyu
2014-06-03 12:51           ` Zhang Haoyu

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=1068437719.3362.24.camel@voyager \
    --to=asanchez@gnome.org \
    --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.