Windows 2000 Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 12 January 2012

AMD Bulldozer hotfix appears - changes Scheduler awareness of CPU from X real cores to 1/2 X real cores

Posted on 19:50 by Unknown
AMD Bulldozer hotfix appears - changes Scheduler awareness of CPU from X real cores to 1/2 X real cores

After appearing briefly a few weeks ago, then disappearing due to reported user complications, the AMD Bulldozer hotfixes for Windows have been re-released, or in the process of being re-released. A helpful supporter of Bitsum pointed this out. Over the course of the day, I noticed an additional download became available (at the first link).


This update DOES change the way the Windows sees your CPU, and can cause Process Lasso to deactivate under some scenarios. This is because it changes the CPU Scheduler's recognition of these AMD processors from (for example) 8 real cores to 4 real cores with 4 hyper-threaded (fake) cores. This is essentially a cheap hack to get performance on par and make use of TurboCore and the intrinsic characteristics of the Bulldozer architecture (e.g. shared L2 cache per 'module' of 2 cores) by telling the scheduler to keep its load on no more than 1/2 of the processors, if it can - and keep any large load off the other cores, if it can.


For example, before this update the below would read "[8 cores: 8 logical]". Meaning, 8 physical (real) cores, 8 total cores.




Now, as the reader can see, the OS thinks there are only 4 real cores, and 4 hyper-threaded (fake) cores. In this way, it is an easy and quick 'hack' to get the Scheduler to play nice with the Bulldozer platform and its 'paired' CPUs with shared L2 caches. Microsoft simply used the pre-existing support for HyperThreaded CPUs.


This will not hurt performance, it will help it. The other cores will get *fully* used under highly threaded situations, they are just avoided. These cores are also now frequently in a 'parked' state, so this update may conserve energy as well.

http://support.microsoft.com/kb/2645594
http://support.microsoft.com/kb/2646060

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Process Lasso v5.0.0.28
    This build continues maintenance, fixing several items and also making a nice improvement to the graph's display. Further, the last sele...
  • Anti-virus software - the #1 cause of PC performance troubles
    Many users realize their anti-virus software consumes massive amounts of system resources, and hope that Process Lasso will somehow keep it ...
  • Optimizing process icon memory use & New core feature coming..
    Two in one post. Yes, here at Bitsum we're going Green by conserving bandwidth ;). Of course, that's just a joke and I fully support...
  • Next update, Options menu gets some changes
    I decided to make the Options menu a little more consistent and move the ProBalnce configuration down with the rest of the rules configurati...
  • Indonesian language added - That makes 11
    Thanks to the work of Ivan Chin, an Indonesian (Bahasa Melayu) translation will be included in v3.99.36. This will be the first time even he...
  • WARNING: Cracks for Process Lasso may modify HOSTS file
    WARNING:  Cracks for Process Lasso have been seen to modify your system HOSTS file so that you can no longer access  bitsum.com  and/or  bit...
  • Process Lasso and WDFME
    Since Process Lasso can be complex for the layman, something we are working on, I wanted to list a set of steps to address the commonly abu...
  • Tightening the Governor
    Most users of Process Lasso are familiar with its core engine, ProcessGovernor.exe. It is the silent background process that applies all pro...
  • The many instances of Chrome
    As many readers of this blog may know, Google Chrome is different from other Windows web browsers. It isolates each of its tabs into an indi...
  • Oh the frustration with this corporate crapware!!
    I now get uninstall feedback, as I solicit it (for better or worse). Once read, I can never go back, lol. Fortunately, most of it is actuall...

Blog Archive

  • ►  2013 (1)
    • ►  March (1)
  • ▼  2012 (6)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ▼  January (2)
      • More about Bulldozer
      • AMD Bulldozer hotfix appears - changes Scheduler a...
  • ►  2011 (166)
    • ►  December (3)
    • ►  November (2)
    • ►  October (2)
    • ►  September (6)
    • ►  August (12)
    • ►  July (14)
    • ►  June (17)
    • ►  May (19)
    • ►  April (13)
    • ►  March (27)
    • ►  February (31)
    • ►  January (20)
  • ►  2010 (203)
    • ►  December (23)
    • ►  November (34)
    • ►  October (38)
    • ►  September (17)
    • ►  August (19)
    • ►  July (19)
    • ►  June (11)
    • ►  May (16)
    • ►  April (8)
    • ►  March (6)
    • ►  February (6)
    • ►  January (6)
  • ►  2009 (43)
    • ►  December (6)
    • ►  November (1)
    • ►  October (10)
    • ►  September (3)
    • ►  August (1)
    • ►  July (9)
    • ►  June (2)
    • ►  May (3)
    • ►  April (4)
    • ►  March (4)
Powered by Blogger.

About Me

Unknown
View my complete profile