Bug 1452589
| Summary: | Review our frequency scaling setup/tuning | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Daniel Bristot de Oliveira <daolivei> | ||||||
| Component: | kernel-rt | Assignee: | Daniel Bristot de Oliveira <daolivei> | ||||||
| kernel-rt sub component: | Other | QA Contact: | Jiri Kastner <jkastner> | ||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||
| Severity: | low | ||||||||
| Priority: | low | CC: | bhu, cww, daolivei, prarit, williams | ||||||
| Version: | 7.4 | ||||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 3.10.0-778.rt56.711 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-04-10 09:07:09 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1420851, 1442258 | ||||||||
| Attachments: |
|
||||||||
|
Description
Daniel Bristot de Oliveira
2017-05-19 09:33:06 UTC
(In reply to Daniel Bristot de Oliveira from comment #0) > Description of problem: > > Our current approach is to tell the customer to disable frequency scaling on > BIOS. However, sometimes the kernel bypass BIOS setup, enabling frequency > scaling. This happened in a specific hardware on BNP. > > It would be nice to have a default setup that guarantees the optimal config > on frequency scaling, even in the case of non-tuned BIOS. > > I do not know if it is better to do it via kernel config or via a tuning > setup, for example, via tuned, but it is something it is nice to > review/set/document. daolivei -- can you give me more details on this? What system, what setup, etc? P. Created attachment 1288060 [details]
system running with kernel 3.10.0-514.el7
Created attachment 1288061 [details]
sosreport running with kernel 3.10.0-514.rt56.420.el7.x86_64
Hi Prarit, This is more about a generic review of our configuration than a problem of a processor. -- Daniel Hi After reviewing the config setup, I saw that the problem was the default frequency scaling governor that was set to: CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y and should be: CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y This change was done in the kernel and the config is now correct. A suggestion of doc text: The real-time kernel is configured to deliver the best on performance and determinism. It means that between power saving and performance, the latter is the choice. In the effort to make RHEL-RT configuration as much compatible with RHEL config, the default CPU frequency scaling governor was set to be the same of RHEL (ONDEMAND) which is not the best option for the RT case. This BZ fixes the problem by setting the PERFORMANCE as the default cpu frequency scaling governor. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0676 |