RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1616038 - rt-setup: include enable-netsocket-tstamp-static-key.c
Summary: rt-setup: include enable-netsocket-tstamp-static-key.c
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rt-setup
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Clark Williams
QA Contact: Jiri Kastner
Marie Hornickova
URL:
Whiteboard:
Depends On:
Blocks: 1532680 1616043
TreeView+ depends on / blocked
 
Reported: 2018-08-14 19:10 UTC by Marcelo Tosatti
Modified: 2018-10-30 11:50 UTC (History)
5 users (show)

Fixed In Version: rt-setup-2.0-1.el7
Doc Type: Enhancement
Doc Text:
*rt-entsk* prevents IPI generation and delay of realtime tasks The chrony daemon, *chronyd*, enables or disables network timestamping, which activates a static key within the kernel. When a static key is enabled or disabled, three inter-processor interrupt (IPIs) are generated to notify other processors of the activation. Previously, rapid activation and deactivation of the *chronyd* static keys led to a delay of a realtime task. Consequently, a latency spike occurred. With this update, systemd starts the *rt-entsk* program, which keeps timestamping enabled and prevents the IPIs from being generated. As a result, IPI generation no longer occurs in a rapid succession, and realtime tasks are no longer delayed due to this bug.
Clone Of:
: 1619407 (view as bug list)
Environment:
Last Closed: 2018-10-30 11:50:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
daemon to enable timestamp on network sockets (969 bytes, text/x-csrc)
2018-08-14 19:12 UTC, Marcelo Tosatti 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3331 0 None None None 2018-10-30 11:50:57 UTC

Description Marcelo Tosatti 2018-08-14 19:10:30 UTC 
Pei Zhang discovered and Daniel Bristot debugged a problem 
where chronyd enables/disables static keys for network timestamping.

The static key enable/disable process includes several IPIs and this causes
additional latency to -RT systems.

To workaround this particular problem, one can enable timestamping
on a socket separately from chronyd.

This is what the attached enable-netsocket-tstamp-static-key.c does.

Please include it in rt-setup so tuned profile can be patched
to start this daemon.
Comment 2 Marcelo Tosatti 2018-08-14 19:12:06 UTC 
Created attachment 1475947 [details]
daemon to enable timestamp on network sockets
Comment 14 errata-xmlrpc 2018-10-30 11:50:46 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, 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-2018:3331
Note You need to log in before you can comment on or make changes to this bug.