From: Hans Reiser <reiser@namesys.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Nishant Sharma <nishantt@cse.iitd.ernet.in>,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: new reiser4 snapshot
Date: Tue, 28 Oct 2003 00:28:16 +0300 [thread overview]
Message-ID: <3F9D8DF0.5000302@namesys.com> (raw)
In-Reply-To: <20031027202556.GI4511@matchmail.com>
Mike Fedyk wrote:
>On Mon, Oct 20, 2003 at 01:44:22PM +0400, Nikita Danilov wrote:
>
>
>>Carl-Daniel Hailfinger writes:
>> > I thought CONFIG_REISER4_LARGE_KEY was force-enabled by now?
>>
>>No. But:
>>
>>1. one has to use -o key=key_short option for mkfs.reiser4 to create
>>file system with small keys.
>>
>>2. lately we mostly test/care about large keys performance and
>>stability.
>>
>>
>
>So why would one want short keys in the first place then?
>
>
>
>
If you are going to access your files in the order that you wrote them
rather than in readdir order, use short keys. You are unlikely to want
to use short keys. large keys were a controversial design decision that
worked. Someday we will write something to allow readdir order to be
creation time order (at the cost of directories not being able to scale
to large sizes effectively), and then short keys will be useful again
for a more significant fraction of users.
maybe config help needs to say that.... nikita, please fix....
--
Hans
next prev parent reply other threads:[~2003-10-27 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:42 new reiser4 snapshot Nikita Danilov
2003-10-17 18:51 ` Hans Reiser
2003-10-19 14:38 ` Nishant Sharma
2003-10-19 18:09 ` Hans Reiser
2003-10-19 22:41 ` Carl-Daniel Hailfinger
2003-10-20 9:44 ` Nikita Danilov
2003-10-27 20:25 ` Mike Fedyk
2003-10-27 21:28 ` Hans Reiser [this message]
2003-10-20 9:37 ` Nikita Danilov
2003-10-20 9:36 ` Nikita Danilov
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=3F9D8DF0.5000302@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@namesys.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=mfedyk@matchmail.com \
--cc=nishantt@cse.iitd.ernet.in \
/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.