All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Peter van Hardenberg <pvh@uvic.ca>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: Plugin modifications to disk format.
Date: Wed, 23 Nov 2005 14:09:35 +0300	[thread overview]
Message-ID: <43844DEF.7060901@namesys.com> (raw)
In-Reply-To: <200511230151.13675.pvh@uvic.ca>

Hello

Peter van Hardenberg wrote:
> More codework today, so more questions.
> 
> inodes:
> ----------
> We would like to add a new field to every inode on disc. 

inode on disk is called stat data in reiser4.
To add a new field to stat data one would have to write sd extension plugin.
reiser4/plugin/item/static_stat.[ch] should help you to get started.

reiser4progs are to be updated to understand new extension plugin.

> This could monopolize 
> the "plugin_data" union on the struct. 

Which struct do you mean?

> Is there a better way? How can this be 
> achieved without breaking format compatibility?
> 
> Storage:
> -----------
> How tightly can these attribute directories be packed? Dominic Giampaulo 
> rejected a similar design to ours for efficiency purposes in the BeFS, but he 
> was not lucky enough to have the advantages of the Reiser storage layer 
> underneath. So... since we have those advantages, how tight can we pack the 
> following:
> 
> Small file with an attribute directory:
> inode
> 	->data
> 	->attributedir_inode
> 		->attributedir_ dir_file
> 			->attribute_inode
> 				->attribute_data 
> 


  reply	other threads:[~2005-11-23 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  9:51 Plugin modifications to disk format Peter van Hardenberg
2005-11-23 11:09 ` Vladimir V. Saveliev [this message]
2005-12-02  9:52 ` 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=43844DEF.7060901@namesys.com \
    --to=vs@namesys.com \
    --cc=pvh@uvic.ca \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@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.