From: Andrew Morton <akpm@digeo.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Paul Larson <plars@linuxtestproject.org>,
lkml <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: Bug in last night's bk test
Date: Mon, 23 Sep 2002 16:13:54 -0700 [thread overview]
Message-ID: <3D8FA032.32193956@digeo.com> (raw)
In-Reply-To: 200209232252.g8NMqN110401@eng2.beaverton.ibm.com
Badari Pulavarty wrote:
>
> >
> > ...
> > Until that's done you'll need to set BIO_MAX_PAGES to 16 in
> > include/linux/bio.h
> >
>
> I am little confused here. I thought IPS driver can handle 64K IO.
> Infact, IPS_MAX_SG is set to 17. So it should be able to handle 68K.
> I have been told that it can handle more than that.. but for some
> reason it was set to 17.
>
> Paul, what kernel are u running ? 2.5.38 ?
>
Current bitkeeper has
#define BIO_MAX_PAGES (256)
That's a megabyte. It works fine with mpage.c. But direct-io.c
is still using BIO_MAX_PAGES. It really is building 1 megabyte
BIOs, which will break just about every device out there.
I think we just ask Linus to do the below until we get it fixed up?
--- 2.5.38-bk2/fs/direct-io.c~direct-io-size Mon Sep 23 16:12:25 2002
+++ 2.5.38-bk2-akpm/fs/direct-io.c Mon Sep 23 16:12:47 2002
@@ -26,7 +26,7 @@
* The largest-sized BIO which this code will assemble, in bytes. Set this
* to PAGE_SIZE if your drivers are broken.
*/
-#define DIO_BIO_MAX_SIZE BIO_MAX_SIZE
+#define DIO_BIO_MAX_SIZE (16*1024)
/*
* How many user pages to map in one call to get_user_pages(). This determines
.
next prev parent reply other threads:[~2002-09-23 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 21:36 Bug in last night's bk test Paul Larson
2002-09-23 22:05 ` Andrew Morton
2002-09-23 22:52 ` Badari Pulavarty
2002-09-23 23:13 ` Andrew Morton [this message]
2002-09-23 23: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=3D8FA032.32193956@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=pbadari@us.ibm.com \
--cc=plars@linuxtestproject.org \
/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.