public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodney Gordon II <meff@pobox.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, "mdew ." <some.nzguy@gmail.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: 2.6.20-ck1
Date: Sun, 18 Feb 2007 00:20:13 -0600	[thread overview]
Message-ID: <1171779613.4740.9.camel@ghreen.sphere> (raw)
In-Reply-To: <1171779357.4740.5.camel@ghreen.sphere>

On Sun, 2007-02-18 at 00:15 -0600, Rodney Gordon II wrote:
> On Sun, 2007-02-18 at 13:38 +1100, Con Kolivas wrote:
> > mdew . writes:
> > 
> > > On 2/16/07, Con Kolivas <kernel@kolivas.org> 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.
> > >>
> > >> Apply to 2.6.20
> > > 
> > > any benchmarks for 2.6.20-ck vs 2.6.20?
> > 
> > Would some -ck user on the mailing list like to perform a set of interbench 
> > benchmarks? They're pretty straight forward to do; see:
> > 
> > http://interbench.kolivas.org
> > 
> > --
> > -ck
> 
> Here are some benches comparing 2.6.18-4-686 (Debian sid stock) and
> 2.6.20-ck1-mt1 (2.6.20-ck1 + sched-idleprio-1.11-2.0.patch)
> 
> I know it's not what was asked for, but it might be useful for review of
> anyone using Debian kernels considering ck patches :)
> 
> Take a look.
> 
> -r

System specs by the way:
Pentium-D 830 3.0GHz Dualcore, 1.5GB RAM, 7200RPM 16MB Cache SATA3 using
AHCI w/ NCQ on.

-- 
Rodney "meff" Gordon II -*- meff@pobox.com
Systems Administrator / Coder Geek -*- Open yourself to OpenSource


  reply	other threads:[~2007-02-18  6:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 10:10 2.6.20-ck1 Con Kolivas
2007-02-16 15:47 ` 2.6.20-ck1 Malte Schröder
2007-02-16 21:35 ` 2.6.20-ck1 Edouard Gomez
2007-02-16 21:45   ` 2.6.20-ck1 Edouard Gomez
2007-02-17  0:53 ` 2.6.20-ck1 Chuck Ebbert
2007-02-17  1:13   ` 2.6.20-ck1 Con Kolivas
2007-02-17  2:15     ` [ck] 2.6.20-ck1 michael chang
2007-02-17  3:17       ` Con Kolivas
2007-02-17 17:28         ` michael chang
2007-02-17 18:45         ` Chuck Ebbert
2007-02-17 21:00           ` Con Kolivas
2007-02-17 21:50             ` michael chang
2007-02-17 23:47             ` Andrew Morton
2007-02-18  0:39               ` 2.6.20-ck1 Con Kolivas
2007-02-18  0:41               ` [ck] 2.6.20-ck1 Radoslaw Szkodzinski
2007-02-18  0:45                 ` 2.6.20-ck1 Con Kolivas
2007-02-17 11:15 ` 2.6.20-ck1 Hugo Vanwoerkom
2007-02-18  2:14 ` 2.6.20-ck1 mdew .
2007-02-18  2:38   ` 2.6.20-ck1 Con Kolivas
2007-02-18  6:05     ` [ck] 2.6.20-ck1 Con Kolivas
2007-02-18  6:15     ` Rodney Gordon II
2007-02-18  6:20       ` Rodney Gordon II [this message]
2007-02-18 16:54     ` 2.6.20-ck1 Ryan M.
2007-02-18 19:00     ` [ck] 2.6.20-ck1 Ash Milsted
2007-02-24 12:12 ` 2.6.20-ck1 Fabio Comolli
2007-02-25  4:34 ` 2.6.20-ck1 Gene Heskett
2007-02-25 10:32   ` 2.6.20-ck1 Con Kolivas
2007-02-25 16:33     ` 2.6.20-ck1 Gene Heskett

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=1171779613.4740.9.camel@ghreen.sphere \
    --to=meff@pobox.com \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=some.nzguy@gmail.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