| Thread Tools |
30th January 2012, 06:37 | #1 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,618
| The AMD FX (Bulldozer) Scheduling Hotfixes Tested The basic building block of Bulldozer is the dual-core module, pictured below. AMD wanted better performance than simple SMT (ala Hyper Threading) would allow but without resorting to full duplication of resources we get in a traditional dual core CPU. The result is a duplication of integer execution resources and L1 caches, but a sharing of the front end and FPU. AMD still refers to this module as being dual-core, although it's a departure from the more traditional definition of the word. In the early days of multi-core x86 processors, dual-core designs were simply two single core processors stuck on the same package. Today we still see simple duplication of identical cores in a single processor, but moving forward it's likely that we'll see more heterogenous multi-core systems. AMD's Bulldozer architecture may be unusual, but it challenges the conventional definition of a core in a way that we're probably going to face one way or another in the not too distant future. The bigger issue with Bulldozer isn't one of core semantics, but rather how threads get scheduled on those cores. Ideally, threads with shared data sets would get scheduled on the same module, while threads that share no data would be scheduled on separate modules. The former allows more efficient use of a module's L2 cache, while the latter guarantees each thread has access to all of a module's resources when there's no tangible benefit to sharing. This ideal scenario isn't how threads are scheduled on Bulldozer today. Instead of intelligent core/module scheduling based on the memory addresses touched by a thread, Windows 7 currently just schedules threads on Bulldozer in order. Starting from core 0 and going up to core 7 in an eight-core FX-8150, Windows 7 will schedule two threads on the first module, then move to the next module, etc... If the threads happen to be working on the same data, then Windows 7's scheduling approach makes sense. If the threads scheduled are working on different data sets however, Windows 7's current treatment of Bulldozer is suboptimal. AMD and Microsoft have been working on a patch to Windows 7 that improves scheduling behavior on Bulldozer. The result are two hotfixes that should both be installed on Bulldozer systems. Read on for our take on what these hotfixes do to Bulldozer's Windows 7 performance. http://www.anandtech.com/show/5448/t...g-patch-tested |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AMD FX-8150 Tested with Latest Windows Hotfixes, Still No Improvement | Stefan Mileschin | WebNews | 0 | 16th January 2012 07:12 |
AMD FX-8150 Bulldozer Tested - Windows 8 vs. Windows 7 Performance | Stefan Mileschin | WebNews | 0 | 28th October 2011 06:50 |
AMD: Bulldozer goes to 11 | jmke | WebNews | 0 | 4th February 2011 13:49 |
Bulldozer has taped out | jmke | WebNews | 0 | 12th November 2009 08:05 |
GMC R-4 Bulldozer Review | jmke | WebNews | 0 | 15th September 2009 08:48 |
GMC R4 Bulldozer Review | jmke | WebNews | 0 | 28th April 2009 13:14 |
Requesting Hotfixes from Microsoft the Easy Way | jmke | WebNews | 0 | 28th August 2008 12:44 |
AMD hotfixes Catalyst 7.9 | jmke | WebNews | 0 | 29th September 2007 21:20 |
Intel said to be scheduling CPU price cuts | Sidney | WebNews | 0 | 9th September 2005 02:13 |
Thread Tools | |
| |