From: Benjamin LaHaise <bcrl@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org, axboe@suse.com
Subject: Re: patch: aio + bio for raw io
Date: Fri, 8 Feb 2002 17:13:27 -0500 [thread overview]
Message-ID: <20020208171327.B12788@redhat.com> (raw)
In-Reply-To: <20020208025313.A11893@redhat.com> <200202082107.g18L7wx26206@eng2.beaverton.ibm.com>
In-Reply-To: <200202082107.g18L7wx26206@eng2.beaverton.ibm.com>; from pbadari@us.ibm.com on Fri, Feb 08, 2002 at 01:07:58PM -0800
On Fri, Feb 08, 2002 at 01:07:58PM -0800, Badari Pulavarty wrote:
> I am looking at the 2.5 patch you sent out. I have few questions/comments:
>
> 1) brw_kvec_async() does not seem to split IO at BIO_MAX_SIZE. I thought
> each bio can handle only BIO_MAX_SIZE (ll_rw_kio() is creating one bio
> for each BIO_MAX_SIZE IO).
Sounds like a needless restriction in bio, especially as one of the design
requirements for the 2.5 block work is that we're able to support large ios
(think 4MB page support).
> And also, currently BIO_MAX_SIZE is only 64K. Infact, if I try to issue
> 64K IO using submit_bio(), I get following BUG() on my QLOGIC controller.
Jens? Also, why does the bio callback return a value? Nothing could ever
possibly use it as far as I can see.
> 2) Could you please make map_user_kvec() generic enough to handle mapping
> of mutliple iovecs to single kvec (to handle readv/writev). I think
> this is a very easy change:
>
> * Add alloc_kvec() and take out the kmalloc() from map_user_kvec().
> * Change map_user_kvec() to start mapping from kvec->veclet[kvec->nr]
> instead of kvec->veclet[0]
>
> This way allocation for kvec to hold all the iovecs can be done at higher
> level and map_user_kvec() can be called in a loop once for each iovec.
Sounds good.
-ben
next prev parent reply other threads:[~2002-02-08 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 7:53 patch: aio + bio for raw io Benjamin LaHaise
2002-02-08 9:40 ` Suparna Bhattacharya
2002-02-08 22:02 ` Benjamin LaHaise
2002-02-11 18:11 ` Suparna Bhattacharya
2002-02-08 21:07 ` Badari Pulavarty
2002-02-08 21:18 ` arjan
2002-02-08 22:13 ` Benjamin LaHaise [this message]
2002-02-08 22:54 ` Linus Torvalds
[not found] ` <200202082254.g18Mspq08299@penguin.transmeta.com>
2002-02-09 0:01 ` Benjamin LaHaise
2002-02-09 0:25 ` Linus Torvalds
2002-02-14 4:46 ` Suparna Bhattacharya
2002-02-11 11:09 ` Jens Axboe
2002-02-11 21:37 ` Badari Pulavarty
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=20020208171327.B12788@redhat.com \
--to=bcrl@redhat.com \
--cc=axboe@suse.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.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.