mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Colin Fowler" <elethiomel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, "Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: Performance loss 2.6.22->22.6.23->2.6.24-rc7 on CPU intensive benchmark on 8 Core Xeon
Date: Wed, 16 Jan 2008 17:34:22 +0000	[thread overview]
Message-ID: <cf3edd8d0801160934u2e39110dv2ccc98081e983b25@mail.gmail.com> (raw)
In-Reply-To: <20080115220641.GC2665@elte.hu>

> there are a handful of 'scheduler feature bits' in
> /proc/sys/kernel/sched_features:
>
> enum {
>         SCHED_FEAT_NEW_FAIR_SLEEPERS    = 1,
>         SCHED_FEAT_WAKEUP_PREEMPT       = 2,
>         SCHED_FEAT_START_DEBIT          = 4,
>         SCHED_FEAT_TREE_AVG             = 8,
>         SCHED_FEAT_APPROX_AVG           = 16,
> };
>

Toggling SCHED_FEAT_NEW_FAIR_SLEEPERS to 0 or
SCHED_FEAT_WAKEUP_PREEMPT to 0 gives me results more inline with my
2.6.22 results. Toggling them both to 0 gives me slightly better
results than 2.6.22!

>   /sys/devices/system/cpu/sched_mc_power_savings
>
> does that change the results?
>

no measurable difference on this toggle that I can see.

  parent reply	other threads:[~2008-01-16 17:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 17:37 Colin Fowler
2008-01-14 18:55 ` Ingo Molnar
2008-01-14 22:42   ` Colin Fowler
2008-01-14 22:43     ` Colin Fowler
2008-01-15 17:01     ` Colin Fowler
2008-01-15 22:06       ` Ingo Molnar
2008-01-15 23:05         ` Colin Fowler
2008-01-16 15:35           ` Ingo Molnar
2008-01-16 16:10             ` Colin Fowler
2008-01-16 16:19               ` Ingo Molnar
2008-01-16 16:38                 ` Colin Fowler
2008-01-16 17:34         ` Colin Fowler [this message]
2008-01-18 10:55           ` Ingo Molnar

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=cf3edd8d0801160934u2e39110dv2ccc98081e983b25@mail.gmail.com \
    --to=elethiomel@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®