public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David J. Wallace" <katana@onetel.com>
To: ck@vds.kolivas.org
Cc: Con Kolivas <kernel@kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.21-ck1
Date: Fri, 4 May 2007 19:59:41 +0100	[thread overview]
Message-ID: <200705041959.47686.katana@onetel.com> (raw)
In-Reply-To: <200705042301.01305.kernel@kolivas.org>

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

On Friday 04 May 2007 14:00, Con Kolivas wrote:
> This patchset is designed to improve system responsiveness and
> interactivity. It is configurable to any workload but the default -ck patch
> is aimed at the desktop and -cks is available with more emphasis on
> serverspace.

Hi Con, 

I have 2.6.21-ck1 running happily on a variety of machines. Everything seems 
fine on both uniprocessor and SMP machines. 

I've been running SD for a couple of weeks now, including alternating between 
a SD patched kernel and an "old" staircase based kernel for a week of that. 
SD seems perfectly smooth. In fact on going back to the old kernel for a day 
I'm sure it felt more "choppy". I don't really do benchmarks, "feel" is more 
relevant to me. Right now I'd say my R4 "feels" better with SD than it has 
for a long time. Nice Job. Thanks for persisiting.

As an aside I realized whilst trying non ck kernels the last few weeks just 
how much of a difference swap prefetch actually makes on a lowish memory 
machine such as this.

Arigatou gozaimashita

David

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

  reply	other threads:[~2007-05-04 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 13:00 2.6.21-ck1 Con Kolivas
2007-05-04 18:59 ` David J. Wallace [this message]
2007-05-05 10:45 ` 2.6.21-ck1 Miguel Figueiredo
2007-05-06  1:45 ` 2.6.21-ck1 Ryan M.

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=200705041959.47686.katana@onetel.com \
    --to=katana@onetel.com \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    /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