| 2018-11-14 10:40:41 |
Colin Ian King |
bug |
|
|
added bug |
| 2018-11-14 10:46:09 |
Colin Ian King |
stress-ng: importance |
Undecided |
High |
|
| 2018-11-14 10:46:11 |
Colin Ian King |
stress-ng: assignee |
|
Colin Ian King (colin-king) |
|
| 2018-11-14 10:46:14 |
Colin Ian King |
stress-ng: status |
New |
Fix Committed |
|
| 2018-11-14 17:36:25 |
Colin Ian King |
description |
the stress-affinity stressor checks to see if sched_setaffinity works, however, in doing so sets the CPU affinity to CPU 0 for all stressors because this is performed at the start of stress-ng and other stressors inherit this affinity setting. Fix this by getting and then setting the same affinity. |
SRU Request [Cosmic]
== Justification ==
When running stress-ng with the affinity stressor, the autodetection of sched_setaffinity currently sets affinity to CPU 0 meaning that the stressors run in the session are pinned to CPU 0.
== Fix ==
Upstream commit http://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=2fea5d0437e918c4cadaa81ba1c3e07073286eff
== Testing ==
Run:
stress-ng --affinity 1 --cpu 4
use top and see that only CPU 0 is being maxed out, other CPUs are less loaded. With the fix at least 4 CPUs are running the cpu stressor
== Regression Potential ==
The fix restores the stress-ng behavior prior to commit 31c7658927, the change is just in the affinity stressor and impact on other stressors with changed functionality is zero. Users of stress-ng with this fix will see their machines being loaded in a more fair and balanced way and stress-ng will max out CPUs, as was originally intended. Regression potential is therefore machines will hit thermal maximums on their CPUs.
----
the stress-affinity stressor checks to see if sched_setaffinity works, however, in doing so sets the CPU affinity to CPU 0 for all stressors because this is performed at the start of stress-ng and other stressors inherit this affinity setting. Fix this by getting and then setting the same affinity. |
|
| 2018-11-14 18:15:11 |
Colin Ian King |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-11-16 09:56:03 |
Timo Aaltonen |
bug task added |
|
stress-ng (Ubuntu) |
|
| 2018-11-16 09:56:17 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-11-16 09:56:17 |
Timo Aaltonen |
bug task added |
|
stress-ng (Ubuntu Cosmic) |
|
| 2018-11-16 10:00:52 |
Timo Aaltonen |
stress-ng (Ubuntu): status |
New |
Fix Released |
|
| 2018-11-16 10:04:01 |
Timo Aaltonen |
stress-ng (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2018-11-16 10:04:03 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2018-11-16 10:04:05 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-cosmic |
|
| 2018-11-16 12:57:14 |
Colin Ian King |
tags |
verification-needed verification-needed-cosmic |
verification-done verification-done-cosmic |
|
| 2018-11-22 09:23:52 |
Colin Ian King |
stress-ng: status |
Fix Committed |
Fix Released |
|
| 2018-11-22 09:24:11 |
Colin Ian King |
stress-ng (Ubuntu Cosmic): assignee |
|
Colin Ian King (colin-king) |
|
| 2018-11-22 09:24:17 |
Colin Ian King |
stress-ng (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2018-11-26 08:07:25 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-11-26 08:17:18 |
Launchpad Janitor |
stress-ng (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
