From: Dave Olien <dmo@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com
Subject: [PATCH] DAC960 2.5.67 add call to blk_queue_bounce_limit
Date: Thu, 17 Apr 2003 14:37:37 -0700 [thread overview]
Message-ID: <20030417213737.GA21387@osdl.org> (raw)
The following patch adds a call to blk_queue_bounce_limit to the
DAC960 driver. Otherwise, it uses bounce buffering more than it
needs to.
-------------------------------------------------------------------------------
diff -ur linux-2.5.67_original/drivers/block/DAC960.c linux-2.5.67_DACpatch/drivers/block/DAC960.c
--- linux-2.5.67_original/drivers/block/DAC960.c 2003-04-07 10:32:18.000000000 -0700
+++ linux-2.5.67_DACpatch/drivers/block/DAC960.c 2003-04-16 10:56:03.000000000 -0700
@@ -1069,6 +1069,7 @@
if (pci_set_dma_mask(Controller->PCIDevice, DAC690_V1_PciDmaMask))
return DAC960_Failure(Controller, "DMA mask out of range");
+ Controller->BounceBufferLimit = DAC690_V1_PciDmaMask;
if ((hw_type == DAC960_PD_Controller) || (hw_type == DAC960_P_Controller)) {
CommandMailboxesSize = 0;
@@ -1271,6 +1272,7 @@
if (pci_set_dma_mask(Controller->PCIDevice, DAC690_V2_PciDmaMask))
return DAC960_Failure(Controller, "DMA mask out of range");
+ Controller->BounceBufferLimit = DAC690_V2_PciDmaMask;
/* This is a temporary dma mapping, used only in the scope of this function */
CommandMailbox =
@@ -2386,6 +2388,7 @@
*/
RequestQueue = &Controller->RequestQueue;
blk_init_queue(RequestQueue, DAC960_RequestFunction, &Controller->queue_lock);
+ blk_queue_bounce_limit(RequestQueue, Controller->BounceBufferLimit);
RequestQueue->queuedata = Controller;
blk_queue_max_hw_segments(RequestQueue,
Controller->DriverScatterGatherLimit);
diff -ur linux-2.5.67_original/drivers/block/DAC960.h linux-2.5.67_DACpatch/drivers/block/DAC960.h
--- linux-2.5.67_original/drivers/block/DAC960.h 2003-04-07 10:32:18.000000000 -0700
+++ linux-2.5.67_DACpatch/drivers/block/DAC960.h 2003-04-16 10:48:37.000000000 -0700
@@ -62,11 +62,6 @@
/*
Define the pci dma mask supported by DAC960 V1 and V2 Firmware Controlers
-
- For now set the V2 mask to only 32 bits. The controller IS capable
- of doing 64 bit dma. But I have yet to find out whether this needs to
- be explicitely enabled in the controller, or of the controller adapts
- automatically.
*/
#define DAC690_V1_PciDmaMask 0xffffffff
@@ -2370,6 +2365,7 @@
unsigned short ControllerScatterGatherLimit;
unsigned short DriverScatterGatherLimit;
unsigned int ControllerUsageCount;
+ u64 BounceBufferLimit;
unsigned int CombinedStatusBufferLength;
unsigned int InitialStatusLength;
unsigned int CurrentStatusLength;
reply other threads:[~2003-04-17 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030417213737.GA21387@osdl.org \
--to=dmo@osdl.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).