Back to bug 2093847
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2022-06-06 08:11:33 UTC | Pool ID | sst_cs_infra_services_rhel_9 | |
| RHEL Program Management | 2022-06-06 08:11:38 UTC | Keywords | FutureFeature | |
| Juri Lelli | 2022-06-06 08:15:07 UTC | CC | bhu, kasmith, kcarcia, rlandry, williams | |
| Red Hat One Jira (issues.redhat.com) | 2022-06-06 08:17:29 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-124323 | |
| Amnon Ilan | 2022-06-23 16:57:42 UTC | CC | ailan | |
| Luiz Capitulino | 2022-06-23 20:33:41 UTC | CC | lcapitulino, mtosatti, nsaenzju | |
| Red Hat Bugzilla | 2022-07-27 22:24:54 UTC | CC | nsaenzju | |
| Jaroslav Škarvada | 2022-07-28 16:33:40 UTC | Status | NEW | ASSIGNED |
| RHEL Program Management | 2022-07-28 16:33:48 UTC | Keywords | Triaged | |
| Jaroslav Škarvada | 2022-08-08 21:46:08 UTC | Keywords | Patch | |
| Robin Hack | 2022-08-09 08:19:29 UTC | Keywords | TestCaseNeeded | |
| Jaroslav Škarvada | 2022-08-09 23:42:55 UTC | Fixed In Version | tuned-2.19.0-0.1.rc1.el9 | |
| Status | ASSIGNED | MODIFIED | ||
| errata-xmlrpc | 2022-08-09 23:52:30 UTC | Status | MODIFIED | ON_QA |
| Mike Stowell | 2022-08-10 15:24:56 UTC | CC | mstowell, rt-qe | |
| John Kacur | 2022-08-10 16:20:02 UTC | CC | jkacur | |
| Shizhao Chen | 2022-08-15 01:48:00 UTC | CC | shichen | |
| Robin Hack | 2022-08-19 11:39:52 UTC | Status | ON_QA | VERIFIED |
| Red Hat Bugzilla | 2022-10-01 08:27:29 UTC | CC | lcapitulino | |
| Beth Uptagrafft | 2022-10-05 19:36:28 UTC | Flags | needinfo?(jskarvad) | |
| Jaroslav Škarvada | 2022-10-11 13:56:46 UTC | Flags | needinfo?(jskarvad) | |
| Jaroslav Škarvada | 2022-10-11 14:06:39 UTC | Doc Text | TuneD realtime profiles now auto determine initial CPU isolation setup. It's handled by built-in function calc_isolated_cores. It expands to the list of cores to isolate and accepts optional argument which specifies how many cores from each socket reserve for housekeeping. If not specified, one core from each socket is reserved for housekeeping. Example: isolated_cores=${f:calc_isolated_cores:2} On machine with 2 sockets, each 4 cores, it will expand to: isolated_cores=2, 3, 6, 7 I.e. cores 0, 1 and 4, 5 will be used for housekeeping. | |
| Doc Type | If docs needed, set a value | Release Note | ||
| Gabi Fialová | 2022-10-12 12:36:31 UTC | Docs Contact | sjanderk | |
| Gabi Fialová | 2022-10-12 12:37:23 UTC | Flags | needinfo?(jskarvad) | |
| CC | gfialova | |||
| Mike Stowell | 2022-10-12 15:31:51 UTC | Version | 9.2 | 9.1 |
| Jaroslav Škarvada | 2022-10-13 11:06:52 UTC | Flags | needinfo?(jskarvad) | |
| Sujata Kurup | 2022-10-14 10:14:55 UTC | CC | skurup | |
| Sujata Kurup | 2022-10-19 08:22:41 UTC | Doc Type | Release Note | Enhancement |
| Gabi Fialová | 2022-10-20 17:57:45 UTC | Doc Text | TuneD realtime profiles now auto determine initial CPU isolation setup. It's handled by built-in function calc_isolated_cores. It expands to the list of cores to isolate and accepts optional argument which specifies how many cores from each socket reserve for housekeeping. If not specified, one core from each socket is reserved for housekeeping. Example: isolated_cores=${f:calc_isolated_cores:2} On machine with 2 sockets, each 4 cores, it will expand to: isolated_cores=2, 3, 6, 7 I.e. cores 0, 1 and 4, 5 will be used for housekeeping. | .TuneD realtime profiles now auto determine initial CPU isolation setup It's handled by built-in function calc_isolated_cores. It expands to the list of cores to isolate and accepts optional argument which specifies how many cores from each socket reserve for housekeeping. If not specified, one core from each socket is reserved for housekeeping. Example: isolated_cores=${f:calc_isolated_cores:2} On machine with 2 sockets, each 4 cores, it will expand to: isolated_cores=2, 3, 6, 7 I.e. cores 0, 1 and 4, 5 will be used for housekeeping. |
| Lenka Špačková | 2022-10-31 16:04:47 UTC | CC | sjanderk | |
| Flags | needinfo?(sjanderk) | |||
| Šárka Jana | 2022-11-01 10:18:03 UTC | Flags | needinfo?(sjanderk) | |
| Šárka Jana | 2022-11-01 11:18:32 UTC | Flags | needinfo?(jskarvad) | |
| Jaroslav Škarvada | 2022-11-01 13:48:39 UTC | Flags | needinfo?(jskarvad) | |
| Šárka Jana | 2022-11-01 14:29:24 UTC | Doc Text | .TuneD realtime profiles now auto determine initial CPU isolation setup It's handled by built-in function calc_isolated_cores. It expands to the list of cores to isolate and accepts optional argument which specifies how many cores from each socket reserve for housekeeping. If not specified, one core from each socket is reserved for housekeeping. Example: isolated_cores=${f:calc_isolated_cores:2} On machine with 2 sockets, each 4 cores, it will expand to: isolated_cores=2, 3, 6, 7 I.e. cores 0, 1 and 4, 5 will be used for housekeeping. | .TuneD real-time profiles now auto determine initial CPU isolation setup TuneD is a service for monitoring your system and optimizing the performance profile. You can also isolate central processing units (CPUs) using the `tuned-profiles-realtime` package to give application threads the most execution time possible. Previously, the real-time profiles for systems running the real-time kernel did not load if you did not specify the list of CPUs to isolate in the `isolated_cores` parameter. With this enhancement, TuneD introduces the `calc_isolated_cores` built-in function that automatically calculates housekeeping and isolated cores lists, and applies the calculation to the `isolated_cores` parameter. With the automatic preset, one core from each socket is reserved for housekeeping, and you can start using the real-time profile without any additional steps. If you want to change the preset, customize the `isolated_cores` parameter by specifying the list of CPUs to isolate. |
| mhou | 2022-11-04 02:41:15 UTC | CC | mhou | |
| errata-xmlrpc | 2022-11-15 00:27:37 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-11-15 11:17:00 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-11-15 11:17:00 UTC | |||
| errata-xmlrpc | 2022-11-15 11:17:07 UTC | Link ID | Red Hat Product Errata RHBA-2022:8321 |
Back to bug 2093847