Bug 1031582

Summary: update example.conf with the tunable params that are present in tuned.
Product: Red Hat Enterprise Linux 7 Reporter: Anton Arapov <anton>
Component: tunaAssignee: John Kacur <jkacur>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Kastner <jkastner>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: bhu, jgalipea, jkacur, jkastner, nobody, poros
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-04 15:46:45 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:

Description Anton Arapov 2013-11-18 10:45:16 UTC
Update example.conf: (this will enable user to see the current setup by tuned sysctl values by default in tuna)

This should have the higher maximum value:
kernel.sched_wakeup_granularity_ns=1000,20000000,

These sysctls should be included:
vm.dirty_background_ratio
kernel.sched_autogroup_enabled
kernel.sched_migration_cost_ns
kernel.sem
vm.max_map_count

Comment 1 Anton Arapov 2013-11-18 10:47:23 UTC
This is not functional change, and doesn't want QE at all. It is a matter of better user experience.

Comment 2 Jenny Severance 2013-11-18 18:00:30 UTC
Can I ask why the QA Contact is set to IDM QE LIST?  This means that the proper QE group will not get notified of bugs against "tuna" ..

Comment 3 Anton Arapov 2013-11-18 19:48:39 UTC
Jenny, feel free to re-assign to the proper QE group. And, perhaps, it will make sense to notify bugzilla-owner to change the default for the "tuna" component. IDM is what it has set when you report a bug against tuna.

Comment 4 Anton Arapov 2014-02-02 18:45:12 UTC
Petr, what is the status of this one? Please don't forget to create an errata for this update.

thanks,

Comment 5 Jiri Kastner 2014-02-03 11:42:38 UTC
(In reply to Anton Arapov from comment #4)
> Petr, what is the status of this one? Please don't forget to create an
> errata for this update.
> 
> thanks,

anton: will be that rhel7 only specific?

Comment 6 Anton Arapov 2014-02-03 12:03:13 UTC
I'd like to see this change in Fedora/upstream as well. It will make the same sense as for RHEL7.

Comment 8 Anton Arapov 2014-02-04 09:09:22 UTC
John, please include the change linked in comment 3 into rhel7's tuna.

thanks!

Comment 9 John Kacur 2014-03-12 00:57:17 UTC
Fixed in 0.11.1-6 and up

Comment 10 John Kacur 2014-03-12 15:05:14 UTC
I didn't realize this needed the blocker flag set since I already had the rhel7.0+ flag, this is ready to go, please approve so I can build

Comment 11 John Kacur 2014-03-12 15:26:03 UTC
Changing to ASSIGNED until I get approval to build with this