For a 4-module, 2-int-core + 1 shared 256-bit floating-point core per module 32-nm processor
1. Standard Mode : 8-int-core+4-shared-fp-core
2. Special Mode 1 : Re-program BIOS/Firmware
4-int-core+4-shared-fp-core. Meaning one-int-core in every module is disabled, so you are left with one-int-core+one-256bit-fp-core.
since half of cores already disabled, so-called cache contention issues reduced. Overclock remaining 4-int-core-4-fp-core to the max
3. Special Mode 2 : Re-program BIOS/Firmware. Hybrid mode
8-int-core+4-shared-fp-core.
Remain-8-int-core to take advantage of multithreading to the maximum.
Software/Firmware coding to ensure scheduling or task switching only on special modules
For example :
Config 0
4 module 8 int-core 4 shared-fp-core : standard BD mode
Config 1A : Core i5-2500K/ Core i7-2600K Mode
4 module 4-int-core 4 shared-fp-core : special mode 1 world-record edition
Config 1B : Core i5-2500K/ Core i7-2600K Mode
3 module 3-int-core 3 shared-fp-core : special mode 1 SuperPI BE Edition max overclock.
1 module 2-int-core 1 shared-fp-core : semi-hyper-threading
Config 2 : Core i5-2400/2500 Mode
2 module 4 int-core 2 shared-fp-core : standard BD mode
2 module 2-int-core 2 shared-fp-core : special mode 1
Config 3 : FOSS Mode : only FOSS people will spend time doing this.
2 module 4 int-core 2 shared-fp-core : standard BD mode
2 module 4-int-core 2 shared-fp-core : special mode 2
say int-core [4,5], [6,7]
- 4 and 6 will take normal tasks and available for standard scheduling.
- 5,7 require special programming and custom scheduling. Since intention is to reduce fp-issue and cache-issue. The intention here is minimize impact to core 4 and 6
I do not have any concrete idea. This is reading www.xtremesystems.org and other recent postings...
1. Standard Mode : 8-int-core+4-shared-fp-core
2. Special Mode 1 : Re-program BIOS/Firmware
4-int-core+4-shared-fp-core. Meaning one-int-core in every module is disabled, so you are left with one-int-core+one-256bit-fp-core.
since half of cores already disabled, so-called cache contention issues reduced. Overclock remaining 4-int-core-4-fp-core to the max
3. Special Mode 2 : Re-program BIOS/Firmware. Hybrid mode
8-int-core+4-shared-fp-core.
Remain-8-int-core to take advantage of multithreading to the maximum.
Software/Firmware coding to ensure scheduling or task switching only on special modules
For example :
Config 0
4 module 8 int-core 4 shared-fp-core : standard BD mode
Config 1A : Core i5-2500K/ Core i7-2600K Mode
4 module 4-int-core 4 shared-fp-core : special mode 1 world-record edition
Config 1B : Core i5-2500K/ Core i7-2600K Mode
3 module 3-int-core 3 shared-fp-core : special mode 1 SuperPI BE Edition max overclock.
1 module 2-int-core 1 shared-fp-core : semi-hyper-threading
Config 2 : Core i5-2400/2500 Mode
2 module 4 int-core 2 shared-fp-core : standard BD mode
2 module 2-int-core 2 shared-fp-core : special mode 1
Config 3 : FOSS Mode : only FOSS people will spend time doing this.
2 module 4 int-core 2 shared-fp-core : standard BD mode
2 module 4-int-core 2 shared-fp-core : special mode 2
say int-core [4,5], [6,7]
- 4 and 6 will take normal tasks and available for standard scheduling.
- 5,7 require special programming and custom scheduling. Since intention is to reduce fp-issue and cache-issue. The intention here is minimize impact to core 4 and 6
I do not have any concrete idea. This is reading www.xtremesystems.org and other recent postings...
Last edited: