public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O16.2int
Date: Sun, 17 Aug 2003 01:00:34 +1000	[thread overview]
Message-ID: <200308170100.34866.kernel@kolivas.org> (raw)
In-Reply-To: <3F3E4293.4080408@cyberone.com.au>

On Sun, 17 Aug 2003 00:41, Nick Piggin wrote:
> Hi Con,
> Up late fixing the scheduler? ;)

Sigh.. yeah it was killing me slowly before and now it's killing me more 
rapidly. Seems I age a year with each patch release. Very occasionally I wish 
I was doing this in daylight hours instead of starting all my hacking at 10pm 
when the family has gone to bed.

> Quick question: have you been Contest-ing your patches much? Would
> you like me to if you haven't the time?

Not as frequently as I'd like no. If you can do nice repeatable runs it would 
be very nice of you thanks. I like to spend as much time as I can testing 
them locally on real world usage, and each time I planned to do some 
benchmarking there was always something else I needed to try after others 
responded. 2.6.0-test3-mm2 #85 doesn't even begin to tell you how many 
kernels I've booted. I've almost rebooted enough to install windows.

If you're interested, this is the script I ran for maximum repeatability in 
minimum timespace of the tests that varied a lot. I had a separate ext3 
partition on another hard disk called /ext3 (explains the command)

oops just noticed you cc'ed lkml. ah what the heck I'll cc it as well
Con

#!/bin/sh
contest -k $1 -o /ext3/dump -n 1 no_load cacherun process_load ctar_load \
xtar_load io_load io_other read_load list_load mem_load dbench_load
contest -k $1 -o /ext3/dump -n 1 process_load ctar_load \
xtar_load io_load io_other read_load list_load mem_load dbench_load
contest -k $1 -o /ext3/dump -n 1 ctar_load \
xtar_load io_load dbench_load
contest -k $1 -o /ext3/dump -n 1 io_load dbench_load
contest -r



  reply	other threads:[~2003-08-16 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-16 11:07 [PATCH] O16.2int Voluspa
2003-08-16 14:09 ` Con Kolivas
2003-08-16 14:41   ` Nick Piggin
2003-08-16 15:00     ` Con Kolivas [this message]
2003-08-16 14:44   ` Voluspa
  -- strict thread matches above, loose matches on Subject: below --
2003-08-17 20:37 Benjamin Weber
2003-08-17 21:47 ` Tom Sightler
2003-08-18  1:21   ` Con Kolivas
2003-08-18 16:51     ` Antonio Vargas
2003-08-18 23:47       ` Con Kolivas
2003-08-16  9:02 Con Kolivas
2003-08-16 13:29 ` Wiktor Wodecki
2003-08-17  7:40 ` Andrew Morton
2003-08-17  9:30   ` Con Kolivas
2003-08-17 14:59   ` Con Kolivas
2003-08-17 21:06     ` Andrew Morton

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=200308170100.34866.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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