Bug 1505158
| Summary: | RFE: Improve RT throttling mechanism [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | kernel-rt | Assignee: | Clark Williams <williams> |
| kernel-rt sub component: | Memory Management | QA Contact: | Jiri Kastner <jkastner> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | bhu, cww, daolivei, dhoward, kernel-eus-qe, mkolaja, salmy, stalexan, toneata, williams |
| Version: | 7.4 | Keywords: | FutureFeature, ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-rt-3.10.0-693.11.1.rt56.629.el7 | Doc Type: | Enhancement |
| Doc Text: |
The current realtime throttling mechanism prevents the starvation of non-realtime tasks by CPU-intensive realtime tasks. When a realtime run queue is throttled, it allows non-realtime tasks to run. If there are not non-realtime tasks, the CPU goes idle. To safely maximize CPU usage by decreasing the CPU idle time, the RT_RUNTIME_GREED scheduler feature has been implemented. When enabled, this feature checks if non-realtime tasks are starving before throttling the realtime task. The RT_RUNTIME_GREED scheduler option guarantees some run time on all CPUs for the non-realtime tasks, while keeping the realtime tasks running as much as possible.
|
Story Points: | --- |
| Clone Of: | 1401061 | Environment: | |
| Last Closed: | 2017-11-30 16:03:50 UTC | Type: | --- |
| 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: | 1401061 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-10-22 16:07:13 UTC
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-2017:3322 |