Bug 1148546
| Summary: | plugin_scheduler add support for runtime detection of processes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Škarvada <jskarvad> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Tereza Cerna <tcerna> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.1 | CC: | bblaskov, jeder, jskarvad, lgoncalv, mgrepl, perfbz, psklenar, qe-baseos-daemons, tcerna, williams |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tuned-2.5.1-3.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Previously plugin_scheduler has no support for tuning of newly spawned processes.
Consequence:
plugin_scheduler could only tune CPU affinity and real-time scheduling attributes of processes that existed when the Tuned profile was applied. Newly spawned processes weren't tuned until Tuned was restarted or the Tuned profile re-appplied.
Fix:
The code was added to plugin_scheduler that monitors newly spawned processes through perf infrastructure and those which match the settings in Tuned profile are also tuned.
Result:
Newly spawned processes are tuned the same way as the processes that existed when the Tuned profile was applied. Moreover if the newly spawned processes exist when the Tuned profile is unapplied, their tuning is rolled back.
|
Story Points: | --- |
| Clone Of: | 1100826 | Environment: | |
| Last Closed: | 2015-11-19 12:20:55 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: | 1100826 | ||
| Bug Blocks: | |||
|
Comment 1
Jaroslav Škarvada
2015-07-04 09:28:22 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://rhn.redhat.com/errata/RHBA-2015-2375.html |