public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: john stultz <johnstul@us.ibm.com>
Cc: Thomas Schlichter <schlicht@uni-mannheim.de>,
	"Prakash K. Cheemplavam" <prakashpublic@gmx.de>,
	"Ronny V. Vindenes" <s864@ii.uib.no>,
	Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	cat@zip.com.au, gawain@freda.homelinux.org,
	gene.heskett@verizon.net, papadako@csd.uoc.gr
Subject: Re: Terrible interactivity with 2.6.0-t9-mm3
Date: Mon, 17 Nov 2003 23:51:26 +0100	[thread overview]
Message-ID: <3FB950EE.10806@gmx.de> (raw)
In-Reply-To: <1069104441.11424.1979.camel@cog.beaverton.ibm.com>

john stultz wrote:
> On Mon, 2003-11-17 at 11:46, Thomas Schlichter wrote:
> 
>>On Monday 17 November 2003 14:12, Prakash K. Cheemplavam wrote:
>>
>>>Ronny V. Vindenes wrote:
>>>
>>>>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.
>>>
>>>Yup, works for me too. Reverting those patches and my machine is smooth
>>>again. :)
> 
> 
> Not configuring the ACPI PM time source in should also work as well. 


> You're correct, I forgot to initialize cpu_khz in the ACPI PM timesource
> init code. This patch fixes that. 

Well I applied your patch without the ones from Thomas Schlichter. Was 
is intended like that or should it be on top of Thomas patches?

I haven't tested thouroughly, but on the first impression your patch 
didn't make things really better, that's why I stoped testing. I just 
did following test:

Running prime95 as task taking 100% CPU) and started up mozilla and 
mailer. This took nearly endlessly. Deaktivating ACPI timer and things 
are fast again, ie. starting mozilla is like no background task is 
runnig. I dunno if it is a not 100% working patch or if it is Nick's 
scheduler, which I am using.

Prakash


  parent reply	other threads:[~2003-11-17 22:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 12:11 Terrible interactivity with 2.6.0-t9-mm3 Ronny V. Vindenes
2003-11-17 13:12 ` 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 [this message]
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=3FB950EE.10806@gmx.de \
    --to=prakashpublic@gmx.de \
    --cc=akpm@osdl.org \
    --cc=cat@zip.com.au \
    --cc=gawain@freda.homelinux.org \
    --cc=gene.heskett@verizon.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=papadako@csd.uoc.gr \
    --cc=s864@ii.uib.no \
    --cc=schlicht@uni-mannheim.de \
    /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