public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Gerdau <mgd@technosis.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, Willy Tarreau <w@1wt.eu>,
	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 16:27:26 +0200	[thread overview]
Message-ID: <200704221627.42788.mgd@technosis.de> (raw)
In-Reply-To: <200704222218.32754.kernel@kolivas.org>

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

> 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?

Have it up running for 40 minutes now and my perljobs show a constant
cpu utilization of 100/50/50 in top most of the time. When the 100% job
goes down to e.g. 70% these 30% are immediately reclaimed by the other
two, i.e. the total sum of all three stays with 2% point of 200%.

From here it seems as if your latest patch did what is was supposed to :-)

Best,
Michael

PS: While these numbercrunching jobs were running I started another
kde session and have my children play supertux for 20 minutes. While
the system occasionally was not as responsive as it is when there
is little load, supertux remained very playable.
-- 
 Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
 Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau       email: mgd@technosis.de
 GPG-keys available on request or at public keyserver

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

  parent reply	other threads:[~2007-04-22 14:27 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
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 [this message]
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=200704221627.42788.mgd@technosis.de \
    --to=mgd@technosis.de \
    --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=mpm@selenic.com \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=w@1wt.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox