From: "Ronny V. Vindenes" <s864@ii.uib.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Terrible interactivity with 2.6.0-t9-mm3
Date: Mon, 17 Nov 2003 13:11:32 +0100 [thread overview]
Message-ID: <1069071092.3238.5.camel@localhost.localdomain> (raw)
Andrew Morton <akpm@osdl.org> writes:
> Gawain Lynch <gawain@freda.homelinux.org> wrote:
> >
> > On Mon, 2003-11-17 at 08:42, Andrew Morton wrote:
> > > Two things to try, please:
> > >
> > > a) Is the problem from Linus's tree? Try 2.6.0-test9 plus
> > >
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm3/broken-out/linus.patch
> > >
> > > b) The only significant scheduler change in mm3 was
> > >
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm3/broken-out/context-switch-accounting-fix.patch
> > >
> > > So please try -mm3 with the above patch reverted with
> > >
> > > patch -R -p1 < context-switch-accounting-fix.patch
> > >
> >
> > Hi Andrew,
> >
> > This is also easily reproducible here with just a kernel compile.
> >
> > I have tried both a) and b) with b) not changing anything, but a)
seems
> > to work... Anything more to try?
> >
>
> Your report has totally confused me. Are you saying that the
jerkiness is
> caused by linus.patch? Or not? Pleas try again ;)
>
I've found that neither linus.patch nor
context-switch-accounting-fix.patch is causing the problem, but rather
acpi-pm-timer-fixes.patch & acpi-pm-timer.patch
With these applied my cpu (athlon64) is detected as 0.0Mhz, bogomips
drops to 50% and anything cpu intensive destroys interactivity. Revert
them and performance is back at -mm2 level.
--
Ronny V. Vindenes <s864@ii.uib.no>
next reply other threads:[~2003-11-17 12:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 12:11 Ronny V. Vindenes [this message]
2003-11-17 13:12 ` Terrible interactivity with 2.6.0-t9-mm3 Prakash K. Cheemplavam
2003-11-17 19:46 ` Thomas Schlichter
2003-11-17 21:27 ` john stultz
2003-11-17 22:44 ` john stultz
2003-11-17 22:51 ` Prakash K. Cheemplavam
2003-11-17 22:55 ` john stultz
2003-11-17 23:04 ` john stultz
2003-11-17 23:46 ` Thomas Schlichter
2003-11-18 22:59 ` linux-2.6.0-test9-mm3_acpi-pm-monotonic-fix_A0 john stultz
2003-11-19 7:34 ` linux-2.6.0-test9-mm3_acpi-pm-monotonic-fix_A0 Thomas Schlichter
2003-11-18 13:24 ` Terrible interactivity with 2.6.0-t9-mm3 Prakash K. Cheemplavam
2003-11-18 16:11 ` Prakash K. Cheemplavam
2003-11-18 18:28 ` john stultz
2003-11-18 16:15 ` Prakash K. Cheemplavam
2003-11-17 13:15 ` Felipe Alfaro Solana
2003-11-17 19:36 ` Andrew Morton
2003-11-17 19:35 ` john stultz
2003-11-18 18:56 ` Dominik Brodowski
2003-11-18 19:18 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
2003-11-16 19:26 CaT
2003-11-16 20:24 ` Prakash K. Cheemplavam
2003-11-16 21:42 ` Andrew Morton
2003-11-16 22:06 ` Arnaldo Carvalho de Melo
2003-11-16 22:13 ` Andrew Morton
2003-11-16 22:18 ` CaT
2003-11-17 0:16 ` Panagiotis Papadakos
2003-11-17 2:20 ` Gawain Lynch
2003-11-17 2:49 ` Andrew Morton
2003-11-17 3:11 ` Gawain Lynch
2003-11-17 3:54 ` Gene Heskett
2003-11-17 4:19 ` Nick Piggin
2003-11-17 4:47 ` Gene Heskett
2003-11-17 5:17 ` Nick Piggin
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=1069071092.3238.5.camel@localhost.localdomain \
--to=s864@ii.uib.no \
--cc=akpm@osdl.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