Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

This is not functional change, and doesn't want QE at all. It is a matter of better user experience.

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" ..

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.

Petr, what is the status of this one? Please don't forget to create an errata for this update.

thanks,

(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?

I'd like to see this change in Fedora/upstream as well. It will make the same sense as for RHEL7.

upstream patch: https://git.kernel.org/cgit/utils/tuna/tuna.git/commit/?id=029deca251faeea85b1fae64d79d9ba8af7dcec4

John, please include the change linked in comment 3 into rhel7's tuna.

thanks!

Fixed in 0.11.1-6 and up

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

Changing to ASSIGNED until I get approval to build with this

https://git.kernel.org/cgit/utils/tuna/tuna.git/commit/?id=029deca251faeea85b1fae64d79d9ba8af7dcec4