Bug 139582

Summary: NFS client doesn't push aio requests aggressively
Product: Red Hat Enterprise Linux 3 Reporter: Chuck Lever <cel>
Component: kernelAssignee: Steve Dickson <steved>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: petrides, riel, steved, xdl-redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:14:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
NFS client now pushes queued aio requests immediately none

Description Chuck Lever 2004-11-16 20:07:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When using aio with NFS files, performance is terrible, or the
application never completes.  The problem is because the NFS client
doesn't push out reads or writes after they are queued by aio.

Version-Release number of selected component (if applicable):
kernel-2.4.21-20.EL

How reproducible:
Always

Steps to Reproduce:
1. See 137830 and use OraSim
2.
3.
    

Actual Results:  OraSim reports "FATAL: Async I/O queue still jammed
after 10000 milliseconds" or other errors that suggests I/O is not
progressing.

Expected Results:  OraSim should run with performance as good as or
better than with normal I/O, without error.

Additional info:

nfs_kvec_read and nfs_kvec_write should flush queued read and write
requests after generic_file_kvec_* returns.

Comment 1 Chuck Lever 2004-11-16 20:08:57 UTC
Created attachment 106843 [details]
NFS client now pushes queued aio requests immediately

For your review and comment

Comment 2 RHEL Program Management 2007-10-19 19:14:02 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.