From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Luca Zini <luca.zini@gmail.com>,
aagaande@gmail.com, rdelcueto@hotmail.com, mingo@elte.hu,
linux-kernel <linux-kernel@vger.kernel.org>,
Alex Chiang <achiang@hp.com>
Subject: Re: scheduler vs hardware? (was Re: another i7 (linux) bug?)
Date: Fri, 22 Jan 2010 10:34:20 +0100 [thread overview]
Message-ID: <1264152860.4283.1442.camel@laptop> (raw)
In-Reply-To: <1264152314.12530.8.camel@marge.simson.net>
On Fri, 2010-01-22 at 10:25 +0100, Mike Galbraith wrote:
> On Fri, 2010-01-22 at 09:51 +0100, Peter Zijlstra wrote:
>
> > My laptop does:
> >
> >
> > # time nice -n 19 lame -b 256 -V0 -h youcantdothat.wav - > /dev/null
>
> > real 0m3.273s
> > user 0m3.217s
> > sys 0m0.022s
> >
> >
> > # time nice -n 0 lame -b 256 -V0 -h youcantdothat.wav - > /dev/null
>
> > real 0m1.121s
> > user 0m1.102s
> > sys 0m0.013s
>
> I don't see any way that can be scheduler (knocks wood). Could it be
> cpufreq? IIRC there is or was an ignore nice gizmo in there.
That's a laptop with full desktop bloat, I'm sure either firefox or evo
farted, or both.
next prev parent reply other threads:[~2010-01-22 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201001211258.23499.luca.zini@gmail.com>
2010-01-21 21:54 ` scheduler vs hardware? (was Re: another i7 (linux) bug?) Alex Chiang
2010-01-22 7:19 ` Mike Galbraith
2010-01-22 8:51 ` Peter Zijlstra
2010-01-22 9:10 ` Mike Galbraith
2010-01-22 9:25 ` Mike Galbraith
2010-01-22 9:34 ` Peter Zijlstra [this message]
2010-01-22 11:22 ` Luca Zini
2010-01-22 15:58 ` Chris Friesen
2010-01-23 9:43 ` Ingo Molnar
2010-01-22 20:15 ` Luca Zini
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=1264152860.4283.1442.camel@laptop \
--to=peterz@infradead.org \
--cc=aagaande@gmail.com \
--cc=achiang@hp.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.zini@gmail.com \
--cc=mingo@elte.hu \
--cc=rdelcueto@hotmail.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