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 1734455 - Add section explicitly requiring the customer follow the vendor low-latency tuning guidelines
Summary: Add section explicitly requiring the customer follow the vendor low-latency t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Realtime_Tuning_Guide
Version: 7.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Klech
QA Contact: Evan McNabb
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-30 14:59 UTC by Clark Williams
Modified: 2019-07-30 15:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-30 15:05:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clark Williams 2019-07-30 14:59:17 UTC
Although it is implied in the document, we should add a section (probably at the start of Chapter 2: General System Tuning) stating that the very first thing that should be done is to follow the system vendors low-latency/real-time tuning guidelines, if they are provided. Both HPE and Dell have documents for adjusting their BIOS settings for a low-latency environment. 

Not sure if we should provide pointers to those documents, especially since tney change frequently. Possibly tips on how to *find* the docs?

Comment 2 Clark Williams 2019-07-30 15:05:30 UTC
I missed the section in Chapter 1 about applying vendor tuning


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