whats bank interweaving?
- Thread starter blackstealth007
- Start date
Like a lot of BIOS settings, you will be hard pressed to notice any difference regardless of how you set it. Unless possibly it causes an instabilty with a particular grouping of hardware.
Like Jeff7 says, people used to talk about it, but they hardly mention it any more.
Memory, and especailly SDRAM has a lot of set up that goes on, using up cycles, before the data can actutally be accessed. The idea of interleaving is that you can have the memory controller setting up one bank of memory while getting data from the other, and switch back and forth, or around 4 if there are 4 banks, therefore hiding some cycles by the overlap. However, I believe memory controllers have gotten more optimized for SDRAM, which gets xeveral successive memory locations with only one very slow major set up, and a "clock" for some number of successive locations, by accessing more successive locations in a row then they used to. On that basis, the difference for interleaving should be harder to see.
Normally you leave BIOS settings on auto unless you are debugging a problem. The BIOSes are usually sophisticated enough to do what is best, or a least can figure out something workable easier than the average home enthusiast. If you want or need to play safe, you start setting things to disable.
Sometimes a BIOS cannot figure out a particular piece of hardware correctly. Then it might enable something that does not function and cause a problem. Or it may think somethig doesn't exist which does, and you can force an enable to pehaps speed things up or otherwise make something work. It is to take care of this type of situation that they stick mysterious settings in the BIOS.
Windows resets a lot of the stuff to its liking (although I think not the memory) while it boots up anyway, or uses its own driver bypassing the BIOS, so getting too worked up about BIOS settings is unnecessay.
Like Jeff7 says, people used to talk about it, but they hardly mention it any more.
Memory, and especailly SDRAM has a lot of set up that goes on, using up cycles, before the data can actutally be accessed. The idea of interleaving is that you can have the memory controller setting up one bank of memory while getting data from the other, and switch back and forth, or around 4 if there are 4 banks, therefore hiding some cycles by the overlap. However, I believe memory controllers have gotten more optimized for SDRAM, which gets xeveral successive memory locations with only one very slow major set up, and a "clock" for some number of successive locations, by accessing more successive locations in a row then they used to. On that basis, the difference for interleaving should be harder to see.
Normally you leave BIOS settings on auto unless you are debugging a problem. The BIOSes are usually sophisticated enough to do what is best, or a least can figure out something workable easier than the average home enthusiast. If you want or need to play safe, you start setting things to disable.
Sometimes a BIOS cannot figure out a particular piece of hardware correctly. Then it might enable something that does not function and cause a problem. Or it may think somethig doesn't exist which does, and you can force an enable to pehaps speed things up or otherwise make something work. It is to take care of this type of situation that they stick mysterious settings in the BIOS.
Windows resets a lot of the stuff to its liking (although I think not the memory) while it boots up anyway, or uses its own driver bypassing the BIOS, so getting too worked up about BIOS settings is unnecessay.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter