All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, Michael Gerdau <mgd@technosis.de>,
	Nick Piggin <npiggin@suse.de>,
	Gene Heskett <gene.heskett@gmail.com>,
	Al Boldi <a1426z@gawab.com>, Bill Huey <billh@gnuppy.monkey.org>,
	Mike Galbraith <efault@gmx.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	Peter Williams <pwil3058@bigpond.net.au>,
	Matt Mackall <mpm@selenic.com>
Subject: Re: [ck] Re: [ANNOUNCE] Staircase Deadline cpu scheduler version 0.45
Date: Sun, 22 Apr 2007 15:07:25 +0200	[thread overview]
Message-ID: <20070422130725.GA16601@1wt.eu> (raw)
In-Reply-To: <200704222218.32754.kernel@kolivas.org>

On Sun, Apr 22, 2007 at 10:18:32PM +1000, Con Kolivas wrote:
> On Sunday 22 April 2007 21:42, Con Kolivas wrote:
> 
> Willy I'm still investigating the idle time and fluctuating load as a separate 
> issue.

OK.

> Is it possible the multiple ocbench processes are naturally 
> synchronising and desynchronising and choosing to sleep and/or run at the 
> same time?

I don't think so. They're independant processes, and I insist on reducing
their X work in order to ensure they don't get perturbated by external
factor. Their work consist in looping 250 ms and waiting 750 ms, then
displaying a new progress line.

> I can remove the idle time entirely by running ocbench at nice 19 
> which means they are all forced to run at basically the same time by the 
> scheduler.

It may indicate some special handling of nice ?

> Anyway the more important part is... Can you test this patch please? Dump
> all the other patches I sent you post 045. Michael, if you could test too
> please?

OK, I will restart from fresh 0.45 and try again.

Regards,
Willy


  reply	other threads:[~2007-04-22 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22  4:41 [ANNOUNCE] Staircase Deadline cpu scheduler version 0.45 Con Kolivas
2007-04-22  7:00 ` Willy Tarreau
2007-04-22  7:27   ` Con Kolivas
2007-04-22  7:31     ` Con Kolivas
2007-04-22  8:06       ` Willy Tarreau
2007-04-22  8:53         ` Con Kolivas
2007-04-22  9:14           ` Willy Tarreau
2007-04-22  9:53             ` Con Kolivas
2007-04-22 11:42             ` Con Kolivas
2007-04-22 12:18               ` [ck] " Con Kolivas
2007-04-22 13:07                 ` Willy Tarreau [this message]
2007-04-22 13:27                   ` Con Kolivas
2007-04-22 14:22                 ` Willy Tarreau
2007-04-22 14:35                   ` Con Kolivas
2007-04-23  7:02                     ` Con Kolivas
2007-04-22 14:27                 ` Michael Gerdau
2007-04-22 14:37                   ` Con Kolivas
2007-04-22  8:02 ` [ck] " Michael Gerdau
2007-04-22 11:09   ` Con Kolivas

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=20070422130725.GA16601@1wt.eu \
    --to=w@1wt.eu \
    --cc=a1426z@gawab.com \
    --cc=billh@gnuppy.monkey.org \
    --cc=ck@vds.kolivas.org \
    --cc=efault@gmx.de \
    --cc=gene.heskett@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgd@technosis.de \
    --cc=mpm@selenic.com \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=wli@holomorphy.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.