Calculating regRegionDelay divides by magical 4096

[deanchester]

I was taking a read through the firefly source to look further in to some of the configuration parameters and noticed that the regRegionDelay function checks to see if the length is larger than m_regRegionXoverLength and then divides by 4096 (which is the default for m_regRegionXoverLength ) should it be divided by m_regRegionXoverLength as this is customisable and not the magical 4096?

sst-elements/src/sst/elements/firefly/ctrlMsgMemory.h

Line 102 in d08a396

if ( nbytes > m_regRegionXoverLength ) {

sst-elements/src/sst/elements/firefly/ctrlMsgMemory.h

Line 103 in d08a396

tmp += (nbytes/4096) * m_regRegionPerPageDelay_ns;

sst-elements/src/sst/elements/firefly/ctrlMsgMemory.h

Line 104 in d08a396

}