From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] SCSI -rc fixes for 2.6.10-rc3
Date: Fri, 10 Dec 2004 21:11:16 +0100 [thread overview]
Message-ID: <20041210201115.GD12581@suse.de> (raw)
In-Reply-To: <1102650988.3814.13.camel@mulgrave>
On Thu, Dec 09 2004, James Bottomley wrote:
> This one is another set of small driver fixes
>
> It is available from:
Here is one more. Currently imm uses page_address() which can crash on
highmem. It's not directly doable to map the pages properly, at least
not without changing some code. In lack of a ->bounce_highio member in
the scsi host template, just set ->unchecked_isa_dma which will just
bounce everything for us. imm isn't performance critical by any stretch
of the imagination, so...
Usually I'd not encourage such a silly hack, but in lack of hardware for
testing (who has it??), this should suffice as it is obviously correct.
Signed-off-by: Jens Axboe <axboe@suse.de>
===== drivers/scsi/imm.c 1.39 vs edited =====
--- 1.39/drivers/scsi/imm.c 2004-08-25 01:09:03 +02:00
+++ edited/drivers/scsi/imm.c 2004-12-10 21:07:29 +01:00
@@ -1140,6 +1140,10 @@
.use_clustering = ENABLE_CLUSTERING,
.can_queue = 1,
.slave_alloc = imm_adjust_queue,
+ .unchecked_isa_dma = 1, /* imm cannot deal with highmem, so
+ * this is an easy trick to ensure
+ * all io pages for this host reside
+ * in low memory */
};
/***************************************************************************
--
Jens Axboe
next prev parent reply other threads:[~2004-12-10 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 3:56 [BK PATCH] SCSI -rc fixes for 2.6.10-rc3 James Bottomley
2004-12-10 20:11 ` Jens Axboe [this message]
2004-12-10 22:55 ` Randy.Dunlap
2004-12-11 14:46 ` James Bottomley
2004-12-11 17:22 ` Jens Axboe
2004-12-11 17:33 ` James Bottomley
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=20041210201115.GD12581@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox