1. 29 3月, 2006 1 次提交
  2. 26 3月, 2006 4 次提交
    • A
      [PATCH] cpufreq_conservative: alternative initialise approach · a159b827
      Alexander Clouter 提交于
      Venki, author of cpufreq_ondemand, came up with a neater way to remove the
      initialiser code from the main loop of my code and out to the point when the
      governor is actually initialised.
      
      Not only does it look but it also feels cleaner, plus its simpler to
      understand.  It also saves a bunch of pointless conditional statements in the
      main loop.
      Signed-off-by: NAlexander Clouter <alex-kernel@digriz.org.uk>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      a159b827
    • A
      [PATCH] cpufreq_conservative: make for_each_cpu() safe · 08a28e2e
      Alexander Clouter 提交于
      All these changes should make cpufreq_conservative safe in regards to the x86
      for_each_cpu cpumask.h changes and whatnot.
      
      Whilst making it safe a number of pointless for loops related to the cpu
      mask's were removed.  I was never comfortable with all those for loops,
      especially as the iteration is over the same data again and again for each
      CPU you had in a single poll, an O(n^2) outcome to frequency scaling.
      
      The approach I use is to assume by default no CPU's exist and it sets the
      requested_freq to zero as a kind of flag, the reasoning is in the source ;)
      If the CPU is queried and requested_freq is zero then it initialises the
      variable to current_freq and then continues as if nothing happened which
      should be the same net effect as before?
      Signed-off-by: NAlexander Clouter <alex-kernel@digriz.org.uk>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      08a28e2e
    • A
      [PATCH] cpufreq_conservative: alter default responsiveness · e8a02572
      Alexander Clouter 提交于
      The sensible approach to making conservative less responsive than ondemand :)
      As mentioned in patch [1/4].  We do not want conservative to shoot through
      all the frequencies, its point (by default) is to slowly move through them.
      
      By default its ten times less responsive.
      Signed-off-by: NAlexander Clouter <alex-kernel@digriz.org.uk>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      e8a02572
    • A
      [PATCH] cpufreq_conservative: aligning of codebase with ondemand · 2c906b31
      Alexander Clouter 提交于
      Since the conservative govenor was released its codebase has drifted from the
      the direction and updates that have been applied to the ondemand govornor.
      
      This patch addresses the lack of updates in that period and brings
      conservative back up to date.  The resulting diff file between
      cpufreq_ondemand.c and cpufreq_conservative.c is now much smaller and shows
      more clearly the differences between the two.
      
      Another reason to do this is ages ago, knowingly, I did a piss poor attempt
      at making conservative less responsive by knocking up
      DEF_SAMPLING_RATE_LATENCY_MULTIPLIER by two orders of magnitude.  I did fix
      this ages ago but in my dis-organisation I must have toasted the diff and
      left it the way it was.  About two weeks ago a user contacted me saying he
      was having problems with the conservative governor with his AMD Athlon XP-M
      2800+ as /sys/devices/system/cpu/cpu0/cpufreq/conservative showed
        sampling_rate_min   9950000
        sampling_rate_max   1360065408
      
      Nine seconds to decide about changing the frequency....not too responsive :)
      Signed-off-by: NAlexander Clouter <alex-kernel@digriz.org.uk>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      2c906b31
  3. 19 1月, 2006 1 次提交
  4. 01 12月, 2005 1 次提交
    • A
      [PATCH] cpufreq_conservative/ondemand: invert meaning of 'ignore nice' · 001893cd
      Alexander Clouter 提交于
      The use of the 'ignore_nice' sysfs file is confusing to anyone using it.
      This removes the sysfs file 'ignore_nice' and in its place creates a
      'ignore_nice_load' entry that defaults to '0'; meaning nice'd processes
      _are_ counted towards the 'business' calculation.
      
      WARNING: this obvious breaks any userland tools that expected ignore_nice'
      to exist, to draw attention to this fact it was concluded on the mailing
      list that the entry should be removed altogether so the userland app breaks
      and so the author can build simple to detect workaround.  Having said that
      it seems currently very few tools even make use of this functionality; all
      I could find was a Gentoo Wiki entry.
      Signed-off-by: NAlexander Clouter <alex-kernel@digriz.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDave Jones <davej@redhat.com>
      001893cd
  5. 28 10月, 2005 1 次提交
  6. 01 6月, 2005 6 次提交
  7. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4