Bug 1593361
| Summary: | Update kernel-rt timer wheel code | ||
|---|---|---|---|
| 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: | Qiao Zhao <qzhao> |
| Status: | CLOSED ERRATA | Docs Contact: | Jaroslav Klech <jklech> |
| Severity: | urgent | ||
| Priority: | unspecified | CC: | bhu, daolivei, jshortt, lgoncalv, williams |
| Version: | 7.6 | ||
| Target Milestone: | rc | ||
| Target Release: | 7.7 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
.The RHEL 7 kernel-rt timer wheel has been updated to a non-cascading timer wheel
The current timer wheel has been switched to a non-cascading wheel which improves the timer subsystem and reduces the overheads on many operations. With the backport of the non-cascading timer wheel, kernel-rt is very close to the upstream kernel in enabling the backport of future improvements.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 12:35:28 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: | 1550584, 1649541, 1723499, 1723502, 1942495 | ||
|
Description
Daniel Bristot de Oliveira
2018-06-20 16:21:53 UTC
Hi Jaroslav! It is still accurate, thanks for the changes, looks better now! -- Daniel (In reply to Daniel Bristot de Oliveira from comment #11) > Hi Jaroslav! > > It is still accurate, thanks for the changes, looks better now! > > -- Daniel Thanks for your verification. By the way, I moved the "." back to the beginning. It is due to AsciiDoc markup, the title must start with a dot. --Jaroslav 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-2019:2043 |