From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: "Dr. Ernst Molitor" <molitor@uni-bonn.de>,
Andrew Morton <akpm@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Fw: PROBLEM: Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used for aha1542" at boot time
Date: Fri, 20 Feb 2004 19:49:45 +0100 [thread overview]
Message-ID: <20040220184945.GD27190@suse.de> (raw)
In-Reply-To: <1077300620.1937.11.camel@mulgrave>
On Fri, Feb 20 2004, James Bottomley wrote:
> On Fri, 2004-02-20 at 00:38, Jens Axboe wrote:
> > Hmm... James, sr_do_ioctl() used to do bouncing for private commands,
> > any reason it doesn't do that anymore?
>
> OK, I've looked through the file history, I can't find anywhere that it
> used to do this.
>
> However, the true solution is to see if we can get scsi_wait_req to go
> through the sg_io code path...that way the block layer will bounce for
> us and we can kill the use_sg == 0 code path in all the drivers.
Yep that'd be my preferred solution as well. Requires bio backing
everything though. I'll hack this up over the weekend.
--
Jens Axboe
next prev parent reply other threads:[~2004-02-20 18:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 1:12 Fw: PROBLEM: Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used for aha1542" at boot time Andrew Morton
2004-02-20 2:18 ` James Bottomley
2004-02-20 8:30 ` Dr. Ernst Molitor
2004-02-20 8:38 ` Jens Axboe
2004-02-20 18:10 ` James Bottomley
2004-02-20 18:49 ` Jens Axboe [this message]
2004-02-20 19:37 ` Jens Axboe
2004-02-23 16:48 ` Jens Axboe
2004-02-23 17:34 ` James Bottomley
2004-02-23 19:04 ` Jens Axboe
2004-02-20 16:49 ` James Bottomley
2004-02-20 17:52 ` Mike Anderson
2004-02-20 18:06 ` James Bottomley
2004-02-20 20:17 ` Dr. Ernst Molitor
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=20040220184945.GD27190@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=molitor@uni-bonn.de \
/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.