All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: reiserfs-list@namesys.com, nikita@namesys.com
Subject: Re: Results of "bk clone" tests with 2.6.2,  reiser4, reiserfs,	ext3, xfs and jfs
Date: Wed, 11 Feb 2004 15:09:38 -0800	[thread overview]
Message-ID: <402AB632.9080006@namesys.com> (raw)
In-Reply-To: <1076525319.1683.44.camel@spc.esa.lanl.gov>

Steven Cole wrote:

>On Wed, 2004-02-11 at 02:32, Steven Cole wrote:
>  
>
>>On Wednesday 11 February 2004 09:12 am, Hans Reiser wrote:
>>    
>>
>>>Steven Cole wrote:
>>>      
>>>
>>>>I used the "-o key=key_short" option when creating the
>>>>reiser4 file system due to getting this message:
>>>>"kernel: WARNING: Key format mismatch. Only small keys are supported."
>>>>        
>>>>
>>>This might have hurt our performance substantially.  Did you
>>>intentionally choose small keys?  If not, Nikita, why did this happen?
>>>      
>>>
>>Well, intentionally _only_ because it seemed the reasonable thing to do
>>in the face of the above warning message.  Tomorrow, I can recompile
>>the reiser4-enabled kernel with the large keys option and mkfs.reiser4
>>again without that key_short option.  I'll let you know if there are any interesting
>>results.
>>
>>Steven
>>    
>>
>
>OK, tomorrow came a day early this week.
>
>I recompiled the 2.6.2 reiser4 kernel with CONFIG_REISER4_LARGE_KEY=y,
>rebooted, and created a reiser4 fs without the key_small option as before.
>
>I repeated the tests using the same bk tree and got very similar results
>to using short keys.
>  
>
Hmmm, we need to look into that.  Thanks Steven.  Zam, please analyze 
just what fs operations this benchmark performs, report it, and then 
analyze why we are slow.

>After that, I umounted and did a fsck.reiser4 and got many errors,
>"12463 fixable corrections". 
>
Well it seems you found a reason for us to delay our release.  Nikita 
will go fix it and then get back to you.

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 23:39 Results of "bk clone" tests with 2.6.2, reiser4, reiserfs, ext3, xfs and jfs Steven Cole
2004-02-11 16:12 ` Hans Reiser
2004-02-11  9:32   ` Steven Cole
2004-02-11 18:48     ` Steven Cole
2004-02-11 23:09       ` Hans Reiser [this message]
2004-02-12  7:12         ` Hans Reiser
2004-02-12 12:54           ` Steven Cole

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=402AB632.9080006@namesys.com \
    --to=reiser@namesys.com \
    --cc=elenstev@mesatop.com \
    --cc=nikita@namesys.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.