[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-aio
Subject:    Re: AIO and vectored I/O support for cifs
From:       Steve French <smfrench () austin ! rr ! com>
Date:       2005-04-04 5:43:50
Message-ID: 4250D416.9090606 () austin ! rr ! com
[Download RAW message or body]

Suparna Bhattacharya wrote:

>cc'ing linux-aio, for the AIO part of the discussion. You might be able
>to find some of your answers in the archives.
>
>there are several tests for AIO - I tend to use Chris Mason's aio-stress
>which can be used to compare performance in terms of throughput for
>streaming reads/writes for different variations of options.
>
>(the following page isn't exactly up-to-date, but should still give
>you some pointers: lse.sf.net/io/aio.html)
>  
>
Thanks - those were lists that I was not aware of.

>>You had mentioned do_sync_read - is there a reason to change the current 
>>call to generic_file_read in the cifs read entry point to do_sync_read.  
>>Some filesystems which export aio routines still call generic_file_read 
>>and others call do_sync_read and it was not obvious to me what that 
>>would change.
>>    
>>
>
>I think you could keep it the way it is - generic_file_read will take care
>of things. But maybe I should comment only after I see your patch. Are
>you planning to post it some time ?
>
>Regards
>Suparna
>  
>
This went in with the patch 
http://cifs.bkbits.net:8080/linux-2.5cifs/gnupatch@424470a3SsdVpix9tJE4NDebxqyRSg
and merged into mainline about six days ago (note that it is disabled by 
default - unless CONFIG_CIFS_EXPERIMENTAL
is selected).
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org.  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
[prev in list] [next in list] [prev in thread] [next in thread]