Back to bug 1401061

Who When What Removed Added
RHEL Program Management 2016-12-02 16:30:18 UTC Keywords FutureFeature
Beth Uptagrafft 2016-12-02 17:02:41 UTC Assignee williams lgoncalv
Beth Uptagrafft 2016-12-02 17:03:06 UTC CC williams
Jiri Kastner 2017-06-08 12:14:13 UTC CC daolivei
Flags needinfo?(daolivei)
Chris Williams 2017-06-19 21:04:45 UTC Priority unspecified medium
CC cww
Blocks 1420851
Severity unspecified medium
Chris Williams 2017-06-19 21:05:11 UTC Doc Type If docs needed, set a value Enhancement
Daniel Bristot de Oliveira 2017-07-14 09:58:13 UTC Assignee lgoncalv daolivei
Flags needinfo?(daolivei)
Beth Uptagrafft 2017-07-14 17:06:55 UTC Blocks 1442258
Beth Uptagrafft 2017-07-14 17:07:36 UTC Status NEW ASSIGNED
Daniel Bristot de Oliveira 2017-07-18 12:26:12 UTC Status ASSIGNED POST
Daniel Bristot de Oliveira 2017-08-14 11:49:23 UTC Status POST MODIFIED
errata-xmlrpc 2017-08-24 15:38:28 UTC Status MODIFIED ON_QA
Marcel Kolaja 2017-09-14 07:40:55 UTC CC mkolaja
Flags needinfo?(bhu)
Sterling Alexander 2017-09-20 16:26:42 UTC CC stalexan
Beth Uptagrafft 2017-09-20 18:01:28 UTC Flags needinfo?(bhu)
Oneata Mircea Teodor 2017-09-21 07:33:32 UTC CC toneata
Marcel Kolaja 2017-09-21 14:25:41 UTC Flags needinfo?(stalexan) needinfo?(daolivei)
Daniel Bristot de Oliveira 2017-10-04 20:42:21 UTC Flags needinfo?(stalexan) needinfo?(daolivei)
Marcel Kolaja 2017-10-18 21:44:07 UTC CC salmy
Flags needinfo?(salmy)
Steve Almy 2017-10-20 12:59:54 UTC Flags needinfo?(salmy)
Oneata Mircea Teodor 2017-10-22 16:07:13 UTC Blocks 1505158
Oneata Mircea Teodor 2017-10-22 16:07:36 UTC Keywords ZStream
Priority medium high
CC dhoward
Beth Uptagrafft 2017-11-01 19:52:51 UTC Doc Text The current real-time throttling mechanism prevents the starvation of non-real-time tasks by CPU intensive real-time tasks. When a real-time runqueue is throttled, it allows non-real-time tasks to run or if there are none the CPU goes idle. In order to safely maximize CPU usage by decreasing the CPU idle time, the RT_RUNTIME_GREED scheduler feature has been implemented. When enabled, this feature will check if non-real-time tasks are starving before throttling the real-time task. This new RT_RUNTIME_GREED scheduler option will guarantee some run time on all CPUs for the non-real-time tasks, while keeping the real-time tasks running as much as possible.
Lenka Špačková 2017-11-13 12:48:47 UTC Docs Contact jsvarova
Jana Heves 2017-12-06 19:19:40 UTC Doc Text The current real-time throttling mechanism prevents the starvation of non-real-time tasks by CPU intensive real-time tasks. When a real-time runqueue is throttled, it allows non-real-time tasks to run or if there are none the CPU goes idle. In order to safely maximize CPU usage by decreasing the CPU idle time, the RT_RUNTIME_GREED scheduler feature has been implemented. When enabled, this feature will check if non-real-time tasks are starving before throttling the real-time task. This new RT_RUNTIME_GREED scheduler option will guarantee some run time on all CPUs for the non-real-time tasks, while keeping the real-time tasks running as much as possible. Improved RT throttling mechanism

The current real-time throttling mechanism prevents the starvation of non-real-time tasks by CPU intensive real-time tasks. When a real-time runqueue is throttled, it allows non-real-time tasks to run or if there are none the CPU goes idle. In order to safely maximize CPU usage by decreasing the CPU idle time, the RT_RUNTIME_GREED scheduler feature has been implemented. When enabled, this feature will check if non-real-time tasks are starving before throttling the real-time task. This new RT_RUNTIME_GREED scheduler option will guarantee some run time on all CPUs for the non-real-time tasks, while keeping the real-time tasks running as much as possible.
Jana Heves 2018-01-08 19:39:10 UTC Doc Text Improved RT throttling mechanism

The current real-time throttling mechanism prevents the starvation of non-real-time tasks by CPU intensive real-time tasks. When a real-time runqueue is throttled, it allows non-real-time tasks to run or if there are none the CPU goes idle. In order to safely maximize CPU usage by decreasing the CPU idle time, the RT_RUNTIME_GREED scheduler feature has been implemented. When enabled, this feature will check if non-real-time tasks are starving before throttling the real-time task. This new RT_RUNTIME_GREED scheduler option will guarantee some run time on all CPUs for the non-real-time tasks, while keeping the real-time tasks running as much as possible.
Improved RT throttling mechanism

The current real-time throttling mechanism prevents the starvation of non-real-time tasks by CPU intensive real-time tasks. When a real-time run queue is throttled, it allows non-real-time tasks to run or if there are none, 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-real-time tasks are starving before throttling the real-time task. As a result, the "RT_RUNTIME_GREED" scheduler option guarantees some run time on all CPUs for the non-real-time tasks, while keeping the real-time tasks running as much as possible.
Jiri Kastner 2018-03-13 15:22:49 UTC Status ON_QA VERIFIED
errata-xmlrpc 2018-04-10 00:07:14 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2018-04-10 09:07:09 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2018-04-10 05:07:09 UTC
errata-xmlrpc 2018-04-10 09:09:31 UTC Link ID Red Hat Product Errata RHSA-2018:0676

Back to bug 1401061