All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Fred -- Speed Up -- <speedup@free.fr>
Cc: reiserfs-list@namesys.com
Subject: Re: Some questions about Reiser4
Date: Sat, 10 May 2003 20:22:24 +0400	[thread overview]
Message-ID: <3EBD2740.7060501@namesys.com> (raw)
In-Reply-To: <001e01c30c03$740efb80$0200a8c0@xpstation>

Fred -- Speed Up -- wrote:

>So, what you call "inodes" within Reiser4 are stat data (last access time,
>right, ...) and a way to find the files's data (not directly the physical
>adress, but a piece of information determining exactly the file), mainly for
>VFS compatibility purposes. Are 'inodes' converted to keys when Reiser4 gets
>them from VFS, or do they represent a physical adress on the disk ?
>
We don't call them inodes, we call them stat data, and stat data are 
stored in the tree where they can be found by their key like everything 
else.

>
>Now I'm going to reformulate the question I asked you about big file storage
>:
>Big files need more than one extent. But according to the documentation,
>there seems to be only one pointer associated to each file. So how can you
>point out multiple extents necessary to store big files, using extent
>pointers in the tree ?
>
>Be sure I'm awaiting the great Hans and his core dev team ;-)
>
>Fred
>
>
>
>  
>


-- 
Hans



  parent reply	other threads:[~2003-05-10 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 20:40 Some questions about Reiser4 Fred -- Speed Up --
2003-04-26 12:48 ` Yury Umanets
2003-04-26 13:28   ` Fred -- Speed Up --
2003-04-26 14:34     ` Yury Umanets
2003-04-26 14:52       ` Fred -- Speed Up --
2003-04-26 15:10         ` Yury Umanets
2003-05-10 16:25           ` Hans Reiser
2003-04-28  5:58         ` Oleg Drokin
2003-05-10 16:22         ` Hans Reiser [this message]
2003-05-10 16:20       ` Hans Reiser
2003-05-10 16:16 ` Hans Reiser

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=3EBD2740.7060501@namesys.com \
    --to=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=speedup@free.fr \
    /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.