From: Martin Steigerwald <Martin@lichtvoll.de>
To: ck@vds.kolivas.org, linux-kernel@vger.kernel.org
Subject: Re: [ck] 2.6.21-ck1-rc1
Date: Tue, 1 May 2007 22:17:14 +0200 [thread overview]
Message-ID: <200705012217.14395.Martin@lichtvoll.de> (raw)
In-Reply-To: <200705012143.38677.Martin@lichtvoll.de>
Am Dienstag 01 Mai 2007 schrieb Martin Steigerwald:
> Am Dienstag 01 Mai 2007 schrieb Con Kolivas:
> > Let's call this a release candidate for 2.6.21-ck1. I've managed to
> > be well enough for enough time to bang this out.
> >
> > http://ck.kolivas.org/patches/pre-releases/2.6.21/2.6.21-ck1-rc1/
[...]
> Hello Con!
>
> Works nicely here. Did my usual stress testing... music playback is
> absolutely smooth.
>
> I will test it during the next 1-2 days at least.
>
> Got ridicolous long releasenames now ;-):
> 2.6.21.1-tp23-sws2-2.2.9.13-ck1-rc1-hotfix-sched-idleprio
> 2.6.21.1-tp42-sws2-2.2.9.13-ck1-rc1-hotfix-sched-idleprio
>
> Feels really very responsive. Those other patches seem to add to the
> responsiveness to sd-0.46 quite well. Can't really tell whether cfs-v7
> or cfs-v8-rc3 is really a slight bit smoother or not. Subjectively
[as I initially thought when comparind sd-0.46 without other ck patches
with cfs]
> seems to be pretty much the same now.
Hmmm, maybe thats the desktop tune patch which sets rr_interval for SD to
6 (from the default of 8) making the difference here.
Anyway its very difficult to tell a difference between ck1-rc1 and
CFS-v8-rc3 from subjective perception. I am really satisfied with both of
them.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
parent reply other threads:[~2007-05-01 20:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200705012143.38677.Martin@lichtvoll.de>]
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=200705012217.14395.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=ck@vds.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
all inboxes | Powered by JetHome®