public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: rwhron@earthlink.net
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] Linux 2.4.18-rc3-jam1
Date: Mon, 25 Feb 2002 00:14:55 +0100	[thread overview]
Message-ID: <20020225001455.A1894@werewolf.able.es> (raw)
In-Reply-To: <20020224150044.GA11858@rushmore>
In-Reply-To: <20020224150044.GA11858@rushmore>; from rwhron@earthlink.net on dom, feb 24, 2002 at 16:00:44 +0100

Hi.

First of all, I never expected this tniny patch collection would origin
such "rivers of e-ink"...
Please, have always present that I can have made some mistake in my
offset re-engineering. But the fact that it at least survives the tests
is good. 

On 20020224 rwhron@earthlink.net wrote:
>2.4.18-rc2-jam1   128  0.80  5.72%    0.190       3.68  0.00000  0.00000  14
>2.4.18-rc4-jam1   128  0.80  5.72%    5.025    6734.19  0.07560  0.00000  14

This is really strange. I have looked at my patches and are the same. What
changed in mainlaine ??

[...]
>
>Below is a snippet of tiobench on random writes.  The rc4-jam1
>included the entire patchset, whereas rc2-jam1 had patches with
>the first two digits < 20.
>

So rc2-jam1 is running without the ide-update (I noticed your system is IDE),
but also without irqrate.
I will reorder the patches so you can apply 0*, 1* and 3* without problems,
then scsi-ide updates. And you can try with/out the ide update.
Do not see what can be related with latency in >=20*, apart from ide and
irqrate...

I do not know if you are already doing this, but I will skip the bproc part
for thins tests. It pollutes system calls with hooks for network, so it can
be hurting in many ways.

I will release a -jam2 with latest vm-27 and reordering the patches.

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-rc4-jam1 #1 SMP Sat Feb 23 16:25:56 CET 2002 i686

  reply	other threads:[~2002-02-24 23:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-24 15:00 [PATCHSET] Linux 2.4.18-rc3-jam1 rwhron
2002-02-24 23:14 ` J.A. Magallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22  4:21 rwhron
2002-02-22  5:35 ` Andrew Morton
2002-02-22  0:50 J.A. Magallon
2002-02-22  7:38 ` Barry K. Nathan
2002-02-23  1:33   ` J.A. Magallon
2002-02-23  8:23     ` Barry K. Nathan
2002-02-23  9:40       ` J.A. Magallon
2002-02-23 23:39         ` Barry K. Nathan
2002-02-24  2:24           ` Barry K. Nathan

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=20020225001455.A1894@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.net \
    /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