[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <20060912032924.GA3677@nickolas.homeunix.com>
Date: Mon, 11 Sep 2006 23:29:24 -0400
From: Nick Orlov <bugfixer@...t.ru>
To: linux-kernel <linux-kernel@...r.kernel.org>,
cpufreq@...ts.linux.org.uk
Cc: Andrew Morton <akpm@...l.org>, Dave Jones <davej@...emonkey.org.uk>
Subject: [PATCH 2.6.18-rc6-mm1 0/2] cpufreq: make it harder for cpu to leave
"hot" mode
Andrew,
I was playing with ondemand cpufreq governor (gotta save on electricity
bills one day :) ) and I've noticed that gameplay become somewhat sluggish.
Especially noticeble in something cpu-power demanding, like quake4.
Quick look at stats/trans_table confirmed that CPU goes out of "hot" mode
way too often.
To make long story short - reverting -mm changes for cpufreq_ondemand.c
helps a _LOT_. I'm not sure if it is something powersave_bias related or
(most probably) due to alignment of "next do_dbs_timer() fire time" which
could make "collect stats" window too short and introduce significant errors.
Have not specifically checked ...
After thinking about the issue for a while I come up with the following tweaks:
First of all I made hysteresis little bit wider (20% instead of 10).
Another idea was to increase "sampling period" once cpu is in "hot" mode.
Second part also have benefits of reducing the load on already overloaded cpu.
Plus it's damn trivial. To simplify further testing I have exposed
"sampling_rate_hot" parameter through sysfs. Setting it to sampling_rate * 10
works for me very well. Now I do not have to switch governor to "performance"
during game sessions.
Tested on AMD64x2 (32 bit mode).
Could you please consider the following patch for inclusion in -mm?
Should be applied after reverting -mm cpufreq_ondemand.c changes.
Thank you,
Nick Orlov
P.S. These are the first patches I'm sending to LKML: please, be patient :)
--
With best wishes,
Nick Orlov.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists