Comment 9 for bug 2051342

I couldn't find this in the benchmark description on Phoronix, so I'm assuming the lowlatency kernel was booted with default parameters. Which means CONFIG_NO_HZ_FULL basically had no effect. This is probably fair for most users who won't specify `nohz_full` kernel parameter and will observe the performance difference between generic and lowlatency as shown by Phoronix tests.

But the claim in this ticket is that `nohz_full` can potentially win back some performance losses caused by CONFIG_HZ=1000. It would be useful if testing could confirm or disprove that. Ideally, Phoronix Test Suite would need to be run on generic, lowlatency without any extra kernel parameters and lowlatency with `nohz_full` parameter.