Bug 2122781
Summary: | [RHEL-9.2] Add cpu socket support for new tuna argparse command line | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Leah Leshchinsky <lleshchi> |
Component: | tuna | Assignee: | Leah Leshchinsky <lleshchi> |
Status: | CLOSED ERRATA | QA Contact: | Qiao Zhao <qzhao> |
Severity: | unspecified | Docs Contact: | Sujata Kurup <skurup> |
Priority: | unspecified | ||
Version: | 9.2 | CC: | bhu, jkacur, mstowell, qzhao, rt-maint, shichen, skurup |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tuna-0.18-7.el9 | Doc Type: | Enhancement |
Doc Text: |
.The `argparse` module now supports configuring CPU sockets
With this enhancement, you can specify a specific CPU socket when you have multiple CPU sockets. You can view the help usage by using the `-h` on a subcommand, for example, `tuna show_threads -h`.
To configure a specific CPU socket, specify the `-S` option with each `tuna` command where you need to use CPU sockets:
----
tuna <command> [-S CPU_SOCKET_LIST]
----
For example, use `tuna show_threads -S 2,3` to view the threads or `tuna show_irqs -S 2,3` to view attached interrupt requests (IRQs).
As a result, this enhancement facilitates CPU usage based on CPU sockets without the need to specify each CPU individually.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-09 08:15:27 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: | |
Embargoed: |
Description
Leah Leshchinsky
2022-08-30 18:51:53 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 (tuna 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-2023:2479 |