From: Steve French <smfrench@austin.rr.com>
To: suparna@in.ibm.com
Cc: hch@lst.de, linux-fsdevel@vger.kernel.org, linux-aio@kvack.org
Subject: Re: AIO and vectored I/O support for cifs
Date: Mon, 04 Apr 2005 00:43:50 -0500 [thread overview]
Message-ID: <4250D416.9090606@austin.rr.com> (raw)
In-Reply-To: <20050404052011.GA4114@in.ibm.com>
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).
prev parent reply other threads:[~2005-04-04 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 21:26 AIO and vectored I/O support for cifs Steve French
2005-04-04 5:20 ` Suparna Bhattacharya
2005-04-04 5:43 ` Steve French [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4250D416.9090606@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=suparna@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.