Bug 2211329
| Summary: | Typo 'iterlave' in memhog man page [rhel8] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Mario Casquero <mcasquer> |
| Component: | numactl | Assignee: | Pingfan Liu <piliu> |
| Status: | CLOSED MIGRATED | QA Contact: | qe-baseos-daemons |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.9 | CC: | chayang, denli, jinzhao |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-25 19:34:16 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: | |||
Hi Mario, Which version do you test against? Thanks (In reply to Pingfan Liu from comment #1) > Hi Mario, > > Which version do you test against? > > > Thanks Hello, With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is reproducible. (In reply to Mario Casquero from comment #2) > (In reply to Pingfan Liu from comment #1) > > Hi Mario, > > > > Which version do you test against? > > > > > > Thanks > Hello, > > With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is > reproducible. It should be fixed at the current release 2.0.16-1. Could you verify it? And if ok, I can close it Thanks (In reply to Pingfan Liu from comment #3) > (In reply to Mario Casquero from comment #2) > > (In reply to Pingfan Liu from comment #1) > > > Hi Mario, > > > > > > Which version do you test against? > > > > > > > > > Thanks > > Hello, > > > > With kernel-4.18.0-494.el8.x86_64 and numactl-2.0.12-13.el8.x86_64 it is > > reproducible. > > It should be fixed at the current release 2.0.16-1. Could you verify it? And > if ok, I can close it > > Thanks [root@dell-per750-24 kar]# rpm -qa | grep numactl numactl-devel-2.0.16-1.el8.x86_64 numactl-libs-2.0.16-1.el8.x86_64 numactl-2.0.16-1.el8.x86_64 # Allocate a 1G region, iterleave across nodes 0,1,2,3, repeat test 4 times Hello Pingfan, I still see the typo at the examples section of memhog man page. Oh, I find the typo. I had thought it appeared in the section " Supported numa-policies: .TP .B interleave Memory will be allocated using round robin on nodes. When memory cannot be allocated on the current interleave, target fall back to other nodes. Multiple nodes may be specified. " But it turned out that I was wrong. Thanks Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: There is a typo at the EXAMPLES section memhog man page: EXAMPLES # Allocate a 1G region, iterleave across nodes 0,1,2,3, repeat test 4 times 'iterleave' has to be changed by 'interleave' which corresponds to the memory policy. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: