Baseline kickstarts per major RHEL release make sense (and, every once in a very great while ... on the U releases)
But for every BIOS/CPU/etc change? No
That's a phenomenal waste of time and energy
Good enough is, as the saying goes, good enough
But for every BIOS/CPU/etc change? No
That's a phenomenal waste of time and energy
Good enough is, as the saying goes, good enough
On CentOS 5.7 and later on Dell you would be correct. Prior to 5.7 there was a bug specific to cstate management and the Dell BIOS that required a work around. This was not optional for CPU latency specific workloads. Good enough was not good enough based on application benchmarks. The bug was worked around with multiple fixes in the 5.7/5.8 timeline. Dell also released a BIOS fix that worked around this as well around the time that CentOS 6 was released but we stayed clear of .0 releases and the BIOS fix had a dependency on the kernel released with C6.