Bug 2122374

Summary: RFE: add nanosecond display option to oslat
Product: Red Hat Enterprise Linux 8 Reporter: John Kacur <jkacur>
Component: rt-testsAssignee: Crystal Wood <crwood>
Status: CLOSED ERRATA QA Contact: Shizhao Chen <shichen>
Severity: unspecified Docs Contact: Sujata Kurup <skurup>
Priority: unspecified    
Version: 8.8CC: bhu, crwood, cyin, jkacur, mstowell, peterx, qzhao, rt-maint, shichen, skurup, williams
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rt-tests-2.4-5.el8 Doc Type: Enhancement
Doc Text:
.The `-W` and `--bucket-width` options have been added to the `oslat` program to measure latency With this enhancement, you can specify a latency range for a single bucket at nanosecond accuracy. Widths that are not multiples of 1000 nanoseconds indicate nanosecond precision. By using the new options, `-W` or `--bucket-width`, you can modify the latency interval between buckets to measure latency within sub-microseconds delay time. For example to set a latency bucket width of 100 nanoseconds for 32 buckets over a duration of 10 seconds to run on CPU range of 1-4 and omit zero bucket size, run the following command: ---- # oslat -b 32 -D 10s -W 100 -z -c 1-4 ---- Note that before using the option, you must determine what level of precision is significant in relation to the error measurement.
Story Points: ---
Clone Of: 2041637 Environment:
Last Closed: 2023-05-16 08:26:12 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:
Bug Depends On: 2041637    
Bug Blocks:    

Comment 18 errata-xmlrpc 2023-05-16 08:26:12 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 (rt-tests 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:2769