This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Request Abstract
Pursuant to maximum precision network time sync, the RFE requests capabilities in POWER/AIX be enhanced to include hardware timekeeping and time synchronization, and the ability to audit compliance. This may include, but is not limited to, changes to the kernel, network driver, PTP client.
Regulatory requirement: MiFID II clock synchronization and timestamping
References:
https://www.esma.europa.eu/sites/default/files/library/2015/11/2015-esma-1464_annex_i_-_draft_rts_and_its_on_mifid_ii_and_mifir.pdf pp. 506-507
Commentary on the regulation:
https://www.bloomberg.com/trading-solutions/blog/mifid-ii-clock-synchronization-advice-dont-drop-the-mic-part-1/
Requirements and Wish list
- Precision MUST be within 100us of UTC.
- Precision is desired to be within 10us of UTC.
Use case: One use case is a low-latency distributed workflow for foreign exchange that traverses several systems. Minimum cycle time for the workflow is in the ballpark of 200us. The application team relies on timestamps at various checkpoints in the workflow to assess performance and issues on a per transaction basis.
The current environment uses software NTP. Concern was raised about skew in timestamps, citing incidents where the start-to-finish durations are posting negative. Tests confirm that the volatility in default software NTP synchronization between servers can be well more than the 100us ballpark needed for sane transaction measures, and are seen to exceed 1ms. NTP doesn't guarantee higher precision. Furthermore, this situation would be non-compliant under upcoming MiFID II regulation.
Prior work
Software PTP was provided in DCR #MR031214247, and that is being evaluated as a potential solution with higher precision.
However, it is not clear that the required or desired precision will be maintained effectively in software. Compliance needs to be proven.
IBM recently confirmed the current state of the latest AIX Mellanox driver and PTP client is that neither supports hardware time synchronization.
Assumptions
- Server: POWER 7+ (minimum p780+), POWER 8 (S824, E850, E880)
- Network card: Mellanox ConnectX-3 PRO 10Gb dual-port
- OS: AIX 7.1 TL3 SP3 or higher
Requested enhancement (above, see Request Abstract)
Partner references
- FSMLabs TimeKeeper: (http://www.mellanox.com/related-docs/whitepapers/WP_Highly_Accurate_Time_Synchronization.pdf)
- Mellanox: https://community.mellanox.com/docs/DOC-2404
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Available in AIX 7.2 TL 3