summaryrefslogtreecommitdiff
path: root/drivers/scsi/be2iscsi
diff options
context:
space:
mode:
authorFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>2010-07-22 20:40:10 +0900
committerJames Bottomley <James.Bottomley@suse.de>2010-08-06 09:23:56 -0500
commitf3506b755f730f199aea3289712f9604ae562319 (patch)
tree63fa1faa404c47b2e9edd03381d8c243e5633d8a /drivers/scsi/be2iscsi
parentfc1caf6eafb30ea185720e29f7f5eccca61ecd60 (diff)
downloadlinux-3.10-f3506b755f730f199aea3289712f9604ae562319.tar.gz
linux-3.10-f3506b755f730f199aea3289712f9604ae562319.tar.bz2
linux-3.10-f3506b755f730f199aea3289712f9604ae562319.zip
[SCSI] 53c700: remove dma_is_consistent usage
This driver is the only user of dma_is_consistent(). We plan to remove this API. The driver uses the API in the following way: BUG_ON(!dma_is_consistent(hostdata->dev, pScript) && L1_CACHE_BYTES < dma_get_cache_alignment()); The above code tries to see if L1_CACHE_BYTES is greater than dma_get_cache_alignment() on sysmtes that can not allocate coherent memory (some old systems can't). James Bottomley exmplained that this is necesary because the driver packs the set of mailboxes into a single coherent area and separates the different usages by a L1 cache stride. So it's fatal if the dma coherence stride is greater than the L1 cache size. He also pointed out that we can kill this checking because we don't hit this BUG_ON on all architectures that actually use the driver. Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/scsi/be2iscsi')
0 files changed, 0 insertions, 0 deletions