From: Hans Reiser <reiser@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Zhihui Zhang <bf20761@binghamton.edu>,
reiserfs-list@namesys.com, vs@namesys.com
Subject: Re: tail policy question
Date: Thu, 13 Nov 2003 21:12:04 -0800 [thread overview]
Message-ID: <3FB46424.4000300@namesys.com> (raw)
In-Reply-To: <20031114170604.GQ1278@backtop.namesys.com>
Alex Zarochentsev wrote:
>On Thu, Nov 13, 2003 at 01:34:07PM -0500, Zhihui Zhang wrote:
>
>
>>Thanks for your and Alex's reply. I poke around a little bit more and
>>find out that the mkfs.c does use ITEM_TAIL40_ID, which happens to have
>>the same value as TAIL_ID (0x6) in the kernel file.
>>
>>
>
>they are from different name spaces.
>
>
>
>
>>However, I am confused
>>when I see the following in plugin.h:
>>
>>PLUGIN_BY_ID(item_plugin, REISER4_ITEM_PLUGIN_TYPE, item);
>>PLUGIN_BY_ID(tail_plugin, REISER4_TAIL_PLUGIN_TYPE, tail);
>>
>>
>
>IFAIK above defines service functions for plugins of different types,
>it does not define concrete plugins. tail_plugin_type should be named
>as tail_policy_plugin for better understanding.
>
>
>
>>The item plugin has TAIL_ID if the item is of tail type. So what is the
>>use of a separate tail_plugin? Plus, the tail_plugin has three IDs
>>defined: NEVER, ALWAYS, and DEFAULT, none of which has a value of 0x6. My
>>guess is that the item plugin for tails are used to manage tails (merge,
>>split, read, write?),
>>
>>
>
>yes
>
>
>
>>while the tail_plugin is used to decide if a
>>conversion between tail format and extent format is needed. If so, the
>>reiser4.h file should have:
>>
>>#define REISER4_TAIL_PLUGIN (DEFAULT_TAIL_ID)
>>
>>instead of
>>
>>#define REISER4_TAIL_PLUGIN (ALWAYS_TAIL_ID)
>>
>>Does this make sense? Please clarify this for me. Thanks.
>>
>>
>
>what i would like to see:
>rename *_TAIL_ID to *_TAIL_POLICY_ID
>DEFAULT_TAIL_POLICY__ID renamed to SMART_TAIL_POLICY_ID
>
>
16K_TAIL_POLICY is more informative....
>#define REISER4_TAIL_POLICY_PLUGIN (one of SMART_TAIL_POLICY_ID ALWAYS_TAIL_POLICY_ID,
> NEVER_TAIL_POLICY_ID)
>
>Does it make things more clear?
>
>Thanks.
>
>
--
Hans
next prev parent reply other threads:[~2003-11-14 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 23:23 tail policy question Zhihui Zhang
2003-11-12 12:56 ` Hans Reiser
2003-11-13 18:34 ` Zhihui Zhang
2003-11-14 17:06 ` Alex Zarochentsev
2003-11-14 5:12 ` Hans Reiser [this message]
2003-11-14 17:27 ` Alex Zarochentsev
2003-11-14 6:02 ` Hans Reiser
2003-11-13 10:27 ` Alex Zarochentsev
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=3FB46424.4000300@namesys.com \
--to=reiser@namesys.com \
--cc=bf20761@binghamton.edu \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
--cc=zam@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.