public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jens Axboe <axboe@suse.de>
Cc: Edward Shishkin <edward@namesys.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: random minor benchmark: Re: Copy 20 tarfiles: ext2 vs (reiser4, unixfile) vs (reiser4,cryptcompress)
Date: Fri, 27 Jan 2006 00:14:57 -0800	[thread overview]
Message-ID: <43D9D681.7020002@namesys.com> (raw)
In-Reply-To: <20060127080625.GS4311@suse.de>

Jens Axboe wrote:

> So the systime quoted above is basically useless, it doesn't reflect the
>
>real time spent in the kernel by far. I think you should note that when
>you post these scores, otherwise you're really showing a skewed picture.
>
>  
>
He wasn't expecting me to post the benchmark, and I frankly only looked
at the real time and forgot there was a systime in there that needed
cutting out when I posted it. My error, not his. I must say though, the
real time makes me quite happy, especially considering how CPUs are just
going to keep getting faster.

Best,

Hans

  reply	other threads:[~2006-01-27  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43D7C6BE.1010804@namesys.com>
2006-01-25 18:59 ` random minor benchmark: Re: Copy 20 tarfiles: ext2 vs (reiser4, unixfile) vs (reiser4,cryptcompress) Hans Reiser
2006-01-26 15:33   ` Jens Axboe
2006-01-26 18:17     ` Edward Shishkin
2006-01-26 18:56       ` Jens Axboe
2006-01-26 20:41         ` Edward Shishkin
2006-01-27  7:43           ` Hans Reiser
2006-01-27  8:09             ` Jens Axboe
2006-01-27  8:06           ` Jens Axboe
2006-01-27  8:14             ` Hans Reiser [this message]
2006-01-27  8:21               ` Jens Axboe
2006-01-27  8:41                 ` Hans Reiser
2006-01-28 16:53         ` Alexander Zarochentsev
2006-01-27  7:30     ` 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=43D9D681.7020002@namesys.com \
    --to=reiser@namesys.com \
    --cc=Reiserfs-List@namesys.com \
    --cc=axboe@suse.de \
    --cc=edward@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox