On 13/09/16 01:44 AM, Alex Deucher wrote:
> From: "monk.liu"
>
> original we use ttm_dma path to allocate GTT bo, which is too much
> slower than the path of ttm_pool, in most cases.
>
> The swiotlb checks don't seem to work and we always end up in the
> slow path even when an IOMMU is available
On Mon, Sep 12, 2016 at 9:17 PM, Michel Dänzer wrote:
> On 13/09/16 01:44 AM, Alex Deucher wrote:
>> From: "monk.liu"
>>
>> original we use ttm_dma path to allocate GTT bo, which is too much
>> slower than the path of ttm_pool, in most cases.
>>
>> The swiotlb checks don't seem to work and we al
Am 12.09.2016 um 18:44 schrieb Alex Deucher:
> From: "monk.liu"
>
> original we use ttm_dma path to allocate GTT bo, which is too much
> slower than the path of ttm_pool, in most cases.
>
> The swiotlb checks don't seem to work and we always end up in the
> slow path even when an IOMMU is availabl
On Mon, Sep 12, 2016 at 2:26 PM, Christian König
wrote:
> Am 12.09.2016 um 18:44 schrieb Alex Deucher:
>>
>> From: "monk.liu"
>>
>> original we use ttm_dma path to allocate GTT bo, which is too much
>> slower than the path of ttm_pool, in most cases.
>>
>> The swiotlb checks don't seem to work a
From: "monk.liu"
original we use ttm_dma path to allocate GTT bo, which is too much
slower than the path of ttm_pool, in most cases.
The swiotlb checks don't seem to work and we always end up in the
slow path even when an IOMMU is available.
Signed-off-by: monk.liu
Reviewed-by: Jammy Zhou
Sig