From: Hans Reiser <reiser@namesys.com>
To: Pallavi Dalya <pallavidalya@yahoo.com>
Cc: reiser-list mailing <reiserfs-list@namesys.com>
Subject: Re: when is it decided that extent pointer is to be created in reiser4
Date: Mon, 21 Feb 2005 10:24:23 -0800 [thread overview]
Message-ID: <421A2757.4000408@namesys.com> (raw)
In-Reply-To: <20050221172615.70993.qmail@web60109.mail.yahoo.com>
Pallavi Dalya wrote:
>hello,
>
> as far as i know tree based file systems use
>extents for managing free space. does reiser4 use a
>bitmap based method or extents to keep track of used
>and free blocks.
>
>
bitmap.
> another issue is that when i tried storing a
>small file an extent pointer was created for the file
>which was also the case for a large file. but to my
>knowledge extent pointers are created for large files
>and in some file systems there is a fixed limit to the
>file size after which it is assigned an extent
>pointer.
>
>
we store in formatted nodes until the file reaches ~16k in size.
>wat is the policy used in reiser4 to decide which
>files should be stored using extent pointers and which
>should not.
> also from what i have observed each file has a
>unique key representing it in reiser4. is there any
>specific key generation algorithm for file names and
>if yes where could i find it. is it possible that
>instead of passing single file names to the key
>generation algorithms we could pass the entire path to
>generate a unique key.
>
>
If you have a limit on the path length, or you make keys variable in
length, yes.
>________________________________________________________________________
>Yahoo! Messenger - Communicate instantly..."Ping"
>your friends today! Download Messenger Now
>http://uk.messenger.yahoo.com/download/index.html
>
>
>
>
prev parent reply other threads:[~2005-02-21 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 17:26 when is it decided that extent pointer is to be created in reiser4 Pallavi Dalya
2005-02-21 18:24 ` Hans Reiser [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=421A2757.4000408@namesys.com \
--to=reiser@namesys.com \
--cc=pallavidalya@yahoo.com \
--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.