I believe that the CPU C-state recommendation is to default to a minimum-latency configuration since that is what most users want and it's required to hit the published latency numbers. The OS can override the default setting, and we will do so for nodes configured as low-latency (essentially we limit it to C1). If the latency is not a concern, then allowing deeper C-states shouldn't break anything. I'm not sure about the "Plug & play BMC detection" setting, but it's still recommended in the R6 docs at https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/dedica... Chris On 7/4/2021 11:49 PM, open infra wrote:
Hi,
As per the hardware requirements, we should disable following settings in the BIOS. I would like to know what's the reason behind these settings.
* CPU C state control disabled
* Plug & play BMC detection disabled
[1] https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/dedica... <https://urldefense.com/v3/__https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/dedicated_storage_hardware.html__;!!AjveYdw8EvQ!OBRG6R8mijUCXJMVYKMUsSFSivC7CkbRz3zxIbfr1iQg17M6fo95aMBKfOfbaB_2VHEC$>
Regards, Danishka
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss