Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Klaus Naumann <spock@mgnet.de>
Cc: Guido Guenther <agx@sigxcpu.org>,
	Linux/MIPS list <linux-mips@oss.sgi.com>,
	klaus@mgnet.de
Subject: Re: [PATCH] sgiwd93.c fix for multiple disks
Date: Tue, 11 Dec 2001 10:55:48 +0100	[thread overview]
Message-ID: <20011211095548.GB399@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0112111034340.2714-300000@spock.mgnet.de>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

On Tue, Dec 11, 2001 at 10:37:11AM +0100, Klaus Naumann wrote:
> Hi all,
> 
> I've done some bonnie++ tests and everything looks good IMHO.
> See attachments (new_speed is with lolo's patch and old_speed without).
> I vote for commit. Cool work !

It looks like this is statistical distortion as some numbers went up.
It looks at least that there is no real difference ...

> Version  1.02       ------Sequential Output------ --Sequential Input- --Random-
>                     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
> ivy            368M  1415  95  2437   7  1003   4  1208  81  2298   6  90.7   2
>                     ------Sequential Create------ --------Random Create--------
>                     -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>               files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
>                  16   235  99 +++++ +++ 13871  98   242  99 +++++ +++   898  99
> ivy,368M,1415,95,2437,7,1003,4,1208,81,2298,6,90.7,2,16,235,99,+++++,+++,13871,98,242,99,+++++,+++,898,99

> Version  1.02       ------Sequential Output------ --Sequential Input- --Random-
>                     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
> ivy            368M  1348  91  2468   7   836   3  1297  87  2178   5  91.0   2
>                     ------Sequential Create------ --------Random Create--------
>                     -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>               files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
>                  16   220  99 +++++ +++ 13440  98   232  99 +++++ +++   780  99
> ivy,368M,1348,91,2468,7,836,3,1297,87,2178,5,91.0,2,16,220,99,+++++,+++,13440,98,232,99,+++++,+++,780,99

I would commit that too with some additional comments that the HPC
is capable of doing scatter-gather but this does not mix with the wd33
framwork which has no support for that.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
Nine nineth on september the 9th              Welcome to the new billenium

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-11 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 20:07 [PATCH] sgiwd93.c fix for multiple disks Florian Lohoff
2001-12-11  1:53 ` Florian Lohoff
2001-12-11  8:58   ` Guido Guenther
2001-12-11  9:37     ` Klaus Naumann
2001-12-11  9:55       ` Florian Lohoff [this message]
2001-12-11 10:06         ` Klaus Naumann

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=20011211095548.GB399@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=agx@sigxcpu.org \
    --cc=klaus@mgnet.de \
    --cc=linux-mips@oss.sgi.com \
    --cc=spock@mgnet.de \
    /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