Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I had these comments
Please take out the line "This allows an application to perform I/O on multiple sources simultaneously. " from the first para. Synchronous IO also works on multiple sources. The IO wait is on a per device basis so if an IO is issued to a device, synchronous IO waits for that IO to complete before issuing another IO to the device. If you want you can change it to "This allows an application to issue multiple IOs to a device and continue with its operation"
Your comment
Sanjay: do we need to explain the sudden drop in delta from 60U to 80U? or am i reading the graph incorrectly?
My response - The drop in the difference is because of user contention. It is common among database applications to see run to run variation of a couple of percent. If you look closely, the blue bar dropped a bit and the orange bar went up a bit so the delta dropped. We can either mention that or modify the graph to take out the 80 user run.