From: rdunlap@xenotime.net (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/2] fix dma_map_sg not to do barriers for each buffer
Date: Wed, 10 Feb 2010 16:41:38 -0800 [thread overview]
Message-ID: <4B735242.8000101@xenotime.net> (raw)
In-Reply-To: <20100211093835I.fujita.tomonori@lab.ntt.co.jp>
On 02/10/10 16:39, FUJITA Tomonori wrote:
> On Wed, 10 Feb 2010 13:27:47 -0800
> Randy Dunlap <rdunlap@xenotime.net> wrote:
>
>> On 02/10/10 12:37, adharmap at codeaurora.org wrote:
>>> From: Abhijeet Dharmapurikar <adharmap@quicinc.com>
>>>
>>> Please refer to the post here
>>> http://lkml.org/lkml/2010/1/4/347
>>>
>>> These changes are to introduce barrierless dma_map_area and dma_unmap_area and
>>> use them to map the buffers in the scatterlist. For the last buffer, call
>>> the normal dma_map_area(aka with barriers) effectively executing the barrier
>>> at the end of the operation.
>>>
>>> Note that the barrierless operations are implemented for few arm
>>> architectures only and I would implement for others once these are okayed by the
>>> community.
>>
>> So when you add these interfaces for other architectures, you will also
>> update Documentation/DMA-API.txt, right??
>
> Seems that you misunderstand him.
>
> He is talking about other "arm" architectures. His patchset improves
> arm's internal implementation (dma_map_area and dma_unmap_area are not
> the DMA API; not exported for driver writers). He meant that the
> patchset doesn't cover all arm architectures.
>
> This is about arm's implementation details and not related with other
> non arm architectures. So no need to update Documentation/DMA-API.txt.
OK, in that case I did misunderstand. Thanks for the info.
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@xenotime.net>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: adharmap@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
adharmap@quicinc.com
Subject: Re: [RFC 0/2] fix dma_map_sg not to do barriers for each buffer
Date: Wed, 10 Feb 2010 16:41:38 -0800 [thread overview]
Message-ID: <4B735242.8000101@xenotime.net> (raw)
In-Reply-To: <20100211093835I.fujita.tomonori@lab.ntt.co.jp>
On 02/10/10 16:39, FUJITA Tomonori wrote:
> On Wed, 10 Feb 2010 13:27:47 -0800
> Randy Dunlap <rdunlap@xenotime.net> wrote:
>
>> On 02/10/10 12:37, adharmap@codeaurora.org wrote:
>>> From: Abhijeet Dharmapurikar <adharmap@quicinc.com>
>>>
>>> Please refer to the post here
>>> http://lkml.org/lkml/2010/1/4/347
>>>
>>> These changes are to introduce barrierless dma_map_area and dma_unmap_area and
>>> use them to map the buffers in the scatterlist. For the last buffer, call
>>> the normal dma_map_area(aka with barriers) effectively executing the barrier
>>> at the end of the operation.
>>>
>>> Note that the barrierless operations are implemented for few arm
>>> architectures only and I would implement for others once these are okayed by the
>>> community.
>>
>> So when you add these interfaces for other architectures, you will also
>> update Documentation/DMA-API.txt, right??
>
> Seems that you misunderstand him.
>
> He is talking about other "arm" architectures. His patchset improves
> arm's internal implementation (dma_map_area and dma_unmap_area are not
> the DMA API; not exported for driver writers). He meant that the
> patchset doesn't cover all arm architectures.
>
> This is about arm's implementation details and not related with other
> non arm architectures. So no need to update Documentation/DMA-API.txt.
OK, in that case I did misunderstand. Thanks for the info.
--
~Randy
next prev parent reply other threads:[~2010-02-11 0:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 20:37 [RFC 0/2] fix dma_map_sg not to do barriers for each buffer adharmap at codeaurora.org
2010-02-10 20:37 ` adharmap
2010-02-10 20:37 ` [PATCH 1/2] dma: define barrierless versions of map and unmap area adharmap at codeaurora.org
2010-02-10 20:37 ` adharmap
2010-02-10 20:37 ` [PATCH 2/2] dma: fix scatter-gather api to use barrierless map/unmap functions adharmap at codeaurora.org
2010-02-10 20:37 ` adharmap
2010-02-10 21:21 ` [RFC 0/2] fix dma_map_sg not to do barriers for each buffer Russell King - ARM Linux
2010-02-10 21:21 ` Russell King - ARM Linux
2010-02-10 23:28 ` Abhijeet Dharmapurikar
2010-02-10 23:28 ` Abhijeet Dharmapurikar
2010-02-10 23:57 ` Russell King - ARM Linux
2010-02-10 23:57 ` Russell King - ARM Linux
2010-02-11 21:36 ` Abhijeet Dharmapurikar
2010-02-11 21:36 ` Abhijeet Dharmapurikar
2010-02-11 10:45 ` Catalin Marinas
2010-02-11 10:45 ` Catalin Marinas
2010-02-11 10:53 ` Catalin Marinas
2010-02-11 10:53 ` Catalin Marinas
2010-02-11 11:01 ` Russell King - ARM Linux
2010-02-11 11:01 ` Russell King - ARM Linux
2010-02-11 11:03 ` Catalin Marinas
2010-02-11 11:03 ` Catalin Marinas
2010-02-11 10:56 ` Russell King - ARM Linux
2010-02-11 10:56 ` Russell King - ARM Linux
2010-02-11 19:13 ` Abhijeet Dharmapurikar
2010-02-11 19:13 ` Abhijeet Dharmapurikar
2010-02-10 21:27 ` Randy Dunlap
2010-02-10 21:27 ` Randy Dunlap
2010-02-10 22:40 ` Russell King - ARM Linux
2010-02-10 22:40 ` Russell King - ARM Linux
2010-02-10 23:10 ` Abhijeet Dharmapurikar
2010-02-10 23:10 ` Abhijeet Dharmapurikar
2010-02-11 0:39 ` FUJITA Tomonori
2010-02-11 0:39 ` FUJITA Tomonori
2010-02-11 0:41 ` Randy Dunlap [this message]
2010-02-11 0:41 ` Randy Dunlap
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=4B735242.8000101@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-arm-kernel@lists.infradead.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 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.