From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC/RFT PATCH 3/5] scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations
Date: Sat, 13 Jul 2013 03:08:27 +0400 [thread overview]
Message-ID: <51E08C6B.2080802@cogentembedded.com> (raw)
In-Reply-To: <20130712222506.GI24642@n2100.arm.linux.org.uk>
Hello.
On 07/13/2013 02:25 AM, Russell King - ARM Linux wrote:
>>> DMA bounce limit is the maximum direct DMA'able memory beyond which
>>> bounce buffers has to be used to perform dma operations. SCSI driver
>>> relies on dma_mask but its calculation is based on max_*pfn which
>>> don't have uniform meaning across architectures. So make use of
>>> dma_max_pfn() which is expected to return the DMAable maximum pfn
>>> value across architectures.
>>> Cc: Russell King <linux@arm.linux.org.uk>
>>> Cc: linux-scsi@vger.kernel.org
>>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> ---
>>> drivers/scsi/scsi_lib.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>>> index 86d5220..e8275fa 100644
>>> --- a/drivers/scsi/scsi_lib.c
>>> +++ b/drivers/scsi/scsi_lib.c
>>> @@ -1668,7 +1668,7 @@ u64 scsi_calculate_bounce_limit(struct Scsi_Host *shost)
>>>
>>> host_dev = scsi_get_device(shost);
>>> if (host_dev && host_dev->dma_mask)
>>> - bounce_limit = *host_dev->dma_mask;
>>> + bounce_limit = dma_max_pfn(host_dev) << PAGE_SHIFT;
>> You definitely forgot -1 here.
> Please explain your point.
Previously, 'bounce_limit' would look like 0xffffffff (unless I'm
mistaken), now it would look like 0xfffff000 which is hardly what we're
looking for, no?
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/RFT PATCH 3/5] scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations
Date: Sat, 13 Jul 2013 03:08:27 +0400 [thread overview]
Message-ID: <51E08C6B.2080802@cogentembedded.com> (raw)
In-Reply-To: <20130712222506.GI24642@n2100.arm.linux.org.uk>
Hello.
On 07/13/2013 02:25 AM, Russell King - ARM Linux wrote:
>>> DMA bounce limit is the maximum direct DMA'able memory beyond which
>>> bounce buffers has to be used to perform dma operations. SCSI driver
>>> relies on dma_mask but its calculation is based on max_*pfn which
>>> don't have uniform meaning across architectures. So make use of
>>> dma_max_pfn() which is expected to return the DMAable maximum pfn
>>> value across architectures.
>>> Cc: Russell King <linux@arm.linux.org.uk>
>>> Cc: linux-scsi at vger.kernel.org
>>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> ---
>>> drivers/scsi/scsi_lib.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>>> index 86d5220..e8275fa 100644
>>> --- a/drivers/scsi/scsi_lib.c
>>> +++ b/drivers/scsi/scsi_lib.c
>>> @@ -1668,7 +1668,7 @@ u64 scsi_calculate_bounce_limit(struct Scsi_Host *shost)
>>>
>>> host_dev = scsi_get_device(shost);
>>> if (host_dev && host_dev->dma_mask)
>>> - bounce_limit = *host_dev->dma_mask;
>>> + bounce_limit = dma_max_pfn(host_dev) << PAGE_SHIFT;
>> You definitely forgot -1 here.
> Please explain your point.
Previously, 'bounce_limit' would look like 0xffffffff (unless I'm
mistaken), now it would look like 0xfffff000 which is hardly what we're
looking for, no?
WBR, Sergei
next prev parent reply other threads:[~2013-07-12 23:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 21:48 [RFC/RFT PATCH 0/5] mm: ARM nobootmem and few dma_mask fixes Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-12 21:48 ` [RFC/RFT PATCH 1/5] block: Rename parameter dma_mask to max_addr for blk_queue_bounce_limit() Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-12 21:48 ` [RFC/RFT PATCH 2/5] mm: dma-mapping: Add dma_max_pfn(dev) helper function Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-12 21:48 ` [RFC/RFT PATCH 3/5] scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-12 21:55 ` Sergei Shtylyov
2013-07-12 21:55 ` Sergei Shtylyov
2013-07-12 22:25 ` Russell King - ARM Linux
2013-07-12 22:25 ` Russell King - ARM Linux
2013-07-12 23:08 ` Sergei Shtylyov [this message]
2013-07-12 23:08 ` Sergei Shtylyov
2013-07-12 23:42 ` Sergei Shtylyov
2013-07-12 23:42 ` Sergei Shtylyov
2013-07-12 23:57 ` Russell King - ARM Linux
2013-07-12 23:57 ` Russell King - ARM Linux
2013-07-12 21:48 ` [RFC/RFT PATCH 4/5] ARM: mm: change max*pfn to include the physical offset of memory Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-13 0:14 ` Russell King - ARM Linux
2013-07-13 0:14 ` Russell King - ARM Linux
2013-07-31 10:56 ` Russell King - ARM Linux
2013-07-31 10:56 ` Russell King - ARM Linux
2013-08-01 2:14 ` Santosh Shilimkar
2013-08-01 2:14 ` Santosh Shilimkar
2013-07-12 21:48 ` [RFC/RFT PATCH 5/5] ARM: mm: Remove bootmem code and switch to NO_BOOTMEM Santosh Shilimkar
2013-07-12 21:48 ` Santosh Shilimkar
2013-07-26 15:10 ` [RFC/RFT PATCH 0/5] mm: ARM nobootmem and few dma_mask fixes Russell King - ARM Linux
2013-07-26 15:10 ` Russell King - ARM Linux
2013-07-26 16:28 ` Santosh Shilimkar
2013-07-26 16:28 ` Santosh Shilimkar
2013-07-26 16:28 ` Santosh Shilimkar
2013-07-29 11:15 ` Russell King - ARM Linux
2013-07-29 11:15 ` Russell King - ARM Linux
2013-07-29 13:26 ` Santosh Shilimkar
2013-07-29 13:26 ` Santosh Shilimkar
2013-07-29 13:40 ` Russell King - ARM Linux
2013-07-29 13:40 ` Russell King - ARM Linux
2013-07-29 13:42 ` Santosh Shilimkar
2013-07-29 13:42 ` Santosh Shilimkar
2013-07-29 13:42 ` Santosh Shilimkar
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=51E08C6B.2080802@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.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 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.