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.
Bug 1784648 - Tuned to support cpuset cgroup for scheduler plug-in
Summary: Tuned to support cpuset cgroup for scheduler plug-in
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tuned
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jaroslav Škarvada
QA Contact: Robin Hack
URL: https://github.com/redhat-performance...
Whiteboard:
Depends On:
Blocks: 1817044 1825061
TreeView+ depends on / blocked
 
Reported: 2019-12-17 22:08 UTC by Andrew Theurer
Modified: 2020-11-04 02:07 UTC (History)
7 users (show)

Fixed In Version: tuned-2.14.0-3.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:03:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4559 0 None None None 2020-11-04 02:03:27 UTC

Description Andrew Theurer 2019-12-17 22:08:57 UTC 
Description of problem:

The scheduler plug-in can move processes to a set of CPUs, but the cpumask is not enforced after (programs can alter their own cpus_allowed mask without requiring permission.  Supporting a cpuset allows the placement to become permanent unless the cpuset is altered [by a user with necessary privilege].
Comment 1 Marcelo Tosatti 2019-12-18 19:35:24 UTC 
Andrew, 

I do not think it is realistic to have the kernel_thread=
patches for OCP 4.4 release. Regarding the OCP feature:

OK, so the interfaces are specified in this spec:

https://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf

Page 46. However they don't seem to be very specific.

What Intel has is:

https://builders.intel.com/docs/networkbuilders/enabling_new_features_in_kubernetes_for_NFV.pdf

On page 7, seem to expose hardware details (probably because they
reached the conclusion that using CAT requires placement to be
aware of the CAT CBM mask).

With CAT (with both HW and Linux kernel interface) one has to decide
which parts of the L3 cache each application can use.

Does this request has management software that knows whether an
application
running on a container has any CAT specific requirements?
If no hardware details are exposed, this has to be decided
on behalf of the application.

To decide on behalf of the application, the answer depends on
how many containers the user wants to pack per host,
whether user has CAT hardware or not.

Once that is done, Tuned can decide on what is the best
interface (with the k8s team). Unfortunately Jaroslav
is on vacation.

Once that is implemented, we can then change the profile
and, if necessary handle the complexities.

I can't find an answer to the above. Whatever is the choice
on your side, we can work on accomodating the requirements
on our side to best match our [currently incomplete] understanding
of the customers usage scenario.
Comment 5 Jaroslav Škarvada 2020-06-02 23:07:20 UTC 
It's tracked in this bugzilla, upstream PR:
https://github.com/redhat-performance/tuned/pull/275
Comment 9 Jaroslav Škarvada 2020-07-03 10:22:02 UTC 
The test revealed bug, upstream fix:
https://github.com/redhat-performance/tuned/pull/284
Comment 17 errata-xmlrpc 2020-11-04 02:03:07 UTC 
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 (tuned bug fix and enhancement update), 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/RHBA-2020:4559
Note You need to log in before you can comment on or make changes to this bug.