Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688864 - G.8275.2 Telecom Profile Timing accuracy
Summary: G.8275.2 Telecom Profile Timing accuracy
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: linuxptp
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Miroslav Lichvar
QA Contact: Yalin.Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-14 15:41 UTC by sushil kulkarni
Modified: 2019-03-14 15:45 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description sushil kulkarni 2019-03-14 15:41:30 UTC
More details:

https://docs.engineering.redhat.com/pages/viewpage.action?pageId=63300108

User Story:

As a 5G cRAN edge cloud provider, I need accurate sub-microsecond PTP clock timing accuracy on RHEL8 with RHEL-RT and RT-KVM in order to deploy cRAN applications on RHEL
verify RHEL timing accuracy < 130ns and offset error is few ns
IPv4/UDP Unicast and 2-Way messaging
Usecase 1- Ordinary Clock (GM and Slave only) 

Measure Timing accuracy on RHEL host and guest with error offset and plot over 24 hour duration


Note You need to log in before you can comment on or make changes to this bug.