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.
Currently we do not using configure with --enable-linux-aio and we should switch to that since Shak has performance results that state it is better than aio=threads.
Comment 1RHEL Program Management
2010-03-07 12:13:45 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 2chellwig@redhat.com
2010-03-07 12:45:35 UTC
Note that Linux aio support gets automatically built if we find libaio and it's headers. So what needs to be done here it pull libaio-devel in as a build requirement.
Also note that we'll need a clone of this bug for libvirt to enable aio=native on the qemu command line,
(In reply to comment #2)
> Note that Linux aio support gets automatically built if we find libaio and it's
> headers. So what needs to be done here it pull libaio-devel in as a build
> requirement.
That's a rpm dependency change
>
> Also note that we'll need a clone of this bug for libvirt to enable aio=native
> on the qemu command line,
Isn't the above sufficient? Alternatively we can change the default ourselves in qemu.
Comment 4chellwig@redhat.com
2010-05-07 11:06:39 UTC
Given that this recently came up on irc, what's the status? Do we still want to change the default aio backend, and if yes do that in libvirt or by patching qemu?
(In reply to comment #4)
> Given that this recently came up on irc, what's the status? Do we still want
> to change the default aio backend, and if yes do that in libvirt or by patching
> qemu?
I think we rather change the default in qemu, there are far too many folks try qemu directly. It's the same like cache=off in the past.
Comment 6chellwig@redhat.com
2010-05-09 17:10:10 UTC
If we're doing this as a RHEL only patch it's easy given that both raw block device (disk/lvm) and nfs support proper AIO. If we want to do this upstream we also need to special case regular files on various local filesystems, especially if they are thinly provisioned.
Dor, is this okay as a RHEL-only patch?