actionjackson4k
Erfahrenes Mitglied
- 60
ja ich denke mal, er wird einfach alles besser machen als die anderen. schneller beim demand und besser runtertakten, wenn man es nicht braucht. er weiss es einfach besser. klugscheisser halt 
KERNEL] uv/oc 2.6.32 for Sense Roms (CFQ/UV950mV/OC1113Mhz/EXT4/Audiomod/CIFS+utf8)
- 172 Antworten
- Letztes Antwortdatum
dj-darkside
Dauer-User
- 229
2.1 Performance
---------------
The CPUfreq governor "performance" sets the CPU statically to the
highest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.2 Powersave
-------------
The CPUfreq governor "powersave" sets the CPU statically to the
lowest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.3 Userspace
-------------
The CPUfreq governor "userspace" allows the user, or any userspace
program running with UID "root", to set the CPU to a specific frequency
by making a sysfs file "scaling_setspeed" available in the CPU-device
directory.
2.4 Ondemand
------------
The CPUfreq governor "ondemand" sets the CPU depending on the
current usage. To do this the CPU must have the capability to
switch the frequency very quickly. There are a number of sysfs file
accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you
want the kernel to look at the CPU usage and to make decisions on
what to do about the frequency. Typically this is set to values of
around '10000' or more. It's default value is (cmp. with users-guide.txt):
transition_latency * 1000
Be aware that transition latency is in ns and sampling_rate is in us, so you
get the same sysfs value by default.
Sampling rate should always get adjusted considering the transition latency
To set the sampling rate 750 times as high as the transition latency
in the bash (as said, 1000 is default), do:
echo `$(($(cat cpuinfo_transition_latency) * 750 / 1000)) \
>ondemand/sampling_rate
show_sampling_rate_min:
The sampling rate is limited by the HW transition latency:
transition_latency * 100
Or by kernel restrictions:
If CONFIG_NO_HZ is set, the limit is 10ms fixed.
If CONFIG_NO_HZ is not set or no_hz=off boot parameter is used, the
limits depend on the CONFIG_HZ option:
HZ=1000: min=20000us (20ms)
HZ=250: min=80000us (80ms)
HZ=100: min=200000us (200ms)
The highest value of kernel and HW latency restrictions is shown and
used as the minimum sampling rate.
show_sampling_rate_max: THIS INTERFACE IS DEPRECATED, DON'T USE IT.
up_threshold: defines what the average CPU usage between the samplings
of 'sampling_rate' needs to be for the kernel to make a decision on
whether it should increase the frequency. For example when it is set
to its default value of '95' it means that between the checking
intervals the CPU needs to be on average more than 95% in use to then
decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When
set to '0' (its default), all processes are counted towards the
'cpu utilisation' value. When set to '1', the processes that are
run with a 'nice' value will not count (and thus be ignored) in the
overall usage calculation. This is useful if you are running a CPU
intensive calculation on your laptop that you do not care how long it
takes to complete as you can 'nice' it and prevent it from taking part
in the deciding process of whether to increase your CPU frequency.
2.5 Conservative
----------------
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
2.6 Interactive
---------------
The CPUfreq governor "interactive" is designed for low latency,
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However
there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU
for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand"
scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS)
at the current frequency before scaling DOWN. This is done to
more accurately determine the cpu workload and the best speed for that
workload. The default is 50ms.
------------------------------------------------------------------------------------------
Quelle: Cyanogenmod Dokumentation
---------------
The CPUfreq governor "performance" sets the CPU statically to the
highest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.2 Powersave
-------------
The CPUfreq governor "powersave" sets the CPU statically to the
lowest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.3 Userspace
-------------
The CPUfreq governor "userspace" allows the user, or any userspace
program running with UID "root", to set the CPU to a specific frequency
by making a sysfs file "scaling_setspeed" available in the CPU-device
directory.
2.4 Ondemand
------------
The CPUfreq governor "ondemand" sets the CPU depending on the
current usage. To do this the CPU must have the capability to
switch the frequency very quickly. There are a number of sysfs file
accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you
want the kernel to look at the CPU usage and to make decisions on
what to do about the frequency. Typically this is set to values of
around '10000' or more. It's default value is (cmp. with users-guide.txt):
transition_latency * 1000
Be aware that transition latency is in ns and sampling_rate is in us, so you
get the same sysfs value by default.
Sampling rate should always get adjusted considering the transition latency
To set the sampling rate 750 times as high as the transition latency
in the bash (as said, 1000 is default), do:
echo `$(($(cat cpuinfo_transition_latency) * 750 / 1000)) \
>ondemand/sampling_rate
show_sampling_rate_min:
The sampling rate is limited by the HW transition latency:
transition_latency * 100
Or by kernel restrictions:
If CONFIG_NO_HZ is set, the limit is 10ms fixed.
If CONFIG_NO_HZ is not set or no_hz=off boot parameter is used, the
limits depend on the CONFIG_HZ option:
HZ=1000: min=20000us (20ms)
HZ=250: min=80000us (80ms)
HZ=100: min=200000us (200ms)
The highest value of kernel and HW latency restrictions is shown and
used as the minimum sampling rate.
show_sampling_rate_max: THIS INTERFACE IS DEPRECATED, DON'T USE IT.
up_threshold: defines what the average CPU usage between the samplings
of 'sampling_rate' needs to be for the kernel to make a decision on
whether it should increase the frequency. For example when it is set
to its default value of '95' it means that between the checking
intervals the CPU needs to be on average more than 95% in use to then
decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When
set to '0' (its default), all processes are counted towards the
'cpu utilisation' value. When set to '1', the processes that are
run with a 'nice' value will not count (and thus be ignored) in the
overall usage calculation. This is useful if you are running a CPU
intensive calculation on your laptop that you do not care how long it
takes to complete as you can 'nice' it and prevent it from taking part
in the deciding process of whether to increase your CPU frequency.
2.5 Conservative
----------------
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
2.6 Interactive
---------------
The CPUfreq governor "interactive" is designed for low latency,
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However
there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU
for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand"
scaling up will always go to MAX, then step down based off of cpu load.
There is only one tuneable value for this governor:
min_sample_time: The ammount of time the CPU must spend (in uS)
at the current frequency before scaling DOWN. This is done to
more accurately determine the cpu workload and the best speed for that
workload. The default is 50ms.
------------------------------------------------------------------------------------------
Quelle: Cyanogenmod Dokumentation
Zuletzt bearbeitet:
G
Gast5050
Gast
- Themenstarter
- #103
Danke, nun vielleicht kann dies jemand ja komplett ins deutsche Übersetzen, kann mir zwar selbst das meiste zusammenreimen aber so extrem gut ist mein englisch leider nicht.
MFG
MFG
dj-darkside
Dauer-User
- 229
Nochn Update... Für Lee Fans oder sonstigen
V5a (Smartass only):
V5a (Smartass only):
- changed default_ramp_up_step and max_ramp_down to 384000
- set smartass as default governor
elknipso
Philosoph
- 654
Danke für den Hinweis, dann wird mal die V5.a getestet .
.
actionjackson4k
Erfahrenes Mitglied
- 60
läuft bei mir perfekt. der klugscheisser mode gefällt mir immer noch am besten. kein ruckeln nach dem wakeup und es kommt mir auch stromsparender vor. kann ich nur weiter empfehlen!
lordofcamster
Stamm-User
- 94
Könnte das mal jemand ins Deutsche transferieren?
Also was der SmartAss bewirkt?
Also was der SmartAss bewirkt?
dj-darkside
Dauer-User
- 229
lordofcamster schrieb:Könnte das mal jemand ins Deutsche transferieren?
Also was der SmartAss bewirkt?
Würde mich auch mal Interessieren wo der Unterschied von SmartAss zu den anderen ist
bzw. welche vorteile dieser bringt.
A
asme
Erfahrenes Mitglied
- 29
smartass governor - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
http://forum.xda-developers.com/showpost.php?p=8847342&postcount=547
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
http://forum.xda-developers.com/showpost.php?p=8847342&postcount=547
dj-darkside
Dauer-User
- 229
Und schon wieder ein Update^^
V5a 1190Mhz kernel (smartass governor is in but not default).
Smartass ist mit in dieser Version drin, aber nicht als Standart ausgewählt. Oder so ähnlich ^^
hmm, aus i-einem grund habe ich immer Bootloops wenn ich ein anderen Kernel mit höhrer MHZ Zahl Flashe -.- weiß einer vielleicht warum?
Beim RCKernel und auch beim v5a 1190 -.-
V5a 1190Mhz kernel (smartass governor is in but not default).
Smartass ist mit in dieser Version drin, aber nicht als Standart ausgewählt. Oder so ähnlich ^^
hmm, aus i-einem grund habe ich immer Bootloops wenn ich ein anderen Kernel mit höhrer MHZ Zahl Flashe -.- weiß einer vielleicht warum?
Beim RCKernel und auch beim v5a 1190 -.-
Zuletzt bearbeitet:
Ro147
Stamm-User
- 54
und für was ist der wifi kernel? kann man den separat flashen, ohne dass was vom UV-kernel verloren geht? thanks!
J
jim_hardcore
Erfahrenes Mitglied
- 47
das ist keine kernel, sondern ein modul.
wifi modul -> [KERNEL] data streaming/VOIP in standby, wifi module for HTC's OTA 2.6.32.15 kernel - xda-developers
steht aber auch beides im OP !
wifi modul -> [KERNEL] data streaming/VOIP in standby, wifi module for HTC's OTA 2.6.32.15 kernel - xda-developers
steht aber auch beides im OP !
dj-darkside
Dauer-User
- 229
Weiß denn einer von euch warum der neue v5a 1190 mh/z kernel nicht auf den Modaco Roms funktioniert? Bekomme da nur Bootloops egal ob mit der r8 oder der r9. Aber auch der RC_Kernel usw^^
Ro147
Stamm-User
- 54
wegen dem hohen takt
dj-darkside
Dauer-User
- 229
myname schrieb:wegen dem hohen takt
Das habe ich mir auch schon gedacht das es an der Taktrate liegt aber die 1113 Mh/z laufen ja auch und auf den anderen Roms funktionieren die Kernel ja doch auch. Warum denn nur bei den Modaco nicht -.-
Ro147
Stamm-User
- 54
Liegt denk nicht am Modaco, da haben diverse Leute probleme damit, siehe xda bei manchen läufts, bei manchen eben nicht. seltsam die welt, wobei die technik ja eig in jedem handy die gleiche sein sollte^^
bei manchen läufts, bei manchen eben nicht. seltsam die welt, wobei die technik ja eig in jedem handy die gleiche sein sollte^^
Contri
Stamm-User
- 26
Also bei mir klappt Sie tadellos und funktioniert einfach nur perfekt.
Ro147
Stamm-User
- 54
gibt neue versionen, scheinbar mit automatischem undervolting Oo
G
Gast5050
Gast
- Themenstarter
- #119
Danke, habe Seite 1 aktualisiert
actionjackson4k
Erfahrenes Mitglied
- 60
funktioniert bei mir einwandfrei. hab den 875mV kernel geflashed und kann mich nicht beschweren. zur akkulaufzeit kann ich noch nicht viel sagen. aber bisher alles im grünen bereich!
Ähnliche Themen
- Shadow128
Shadow128