From: Andrew Morton <akpm@zip.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.5.23 mpage io vs queue_max_sectors
Date: Wed, 19 Jun 2002 17:38:25 -0700 [thread overview]
Message-ID: <3D112401.6975E890@zip.com.au> (raw)
In-Reply-To: 20020620002105.GL25360@holomorphy.com
William Lee Irwin III wrote:
>
> This has been haunting me for a while on a 4 cpu Sequent S-quad with
> 4GB of RAM, and a tray of 12 9GB DCHS09X's attached to a QLogicISP1020.
> People keep saying "hands off" ... so here I am passing the buck.
>
> Kernel BUG at ll_rw_blk.c:1639
This is happening because we have BIO_MAX_SIZE = 64k,
but that particular driver doesn't like requests which are
that big.
This is the issuewhich Adam, Jens and I have been discussing.
Looks like the preferred solution is an add_page_to_bio() API
in the block layer.
But it's not there yet, so in the short-term, please just do
-#define MPAGE_BIO_MAX_SIZE BIO_MAX_SIZE
+#define MPAGE_BIO_MAX_SIZE 16384
in fs/mpage.c
-
next prev parent reply other threads:[~2002-06-20 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 0:21 [BUG] 2.5.23 mpage io vs queue_max_sectors William Lee Irwin III
2002-06-20 0:38 ` Andrew Morton [this message]
2002-06-20 0:43 ` William Lee Irwin III
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=3D112401.6975E890@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox