Re: [Xen-devel] [PATCH] modify the IO_TLB_SEGSIZE to io_tlb_segsize configurable as flexible requirement about SW-IOMMU.

[David Vrabel]

On 06/02/15 00:10, Wang, Xiaoming wrote:
> 
> 
>> -----Original Message-----
>> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
>> Sent: Friday, February 6, 2015 3:33 AM
>> To: Wang, Xiaoming
>> Cc: ralf@xxxxxxxxxxxxxx; boris.ostrovsky@xxxxxxxxxx;
>> david.vrabel@xxxxxxxxxx; linux-mips@xxxxxxxxxxxxxx; linux-
>> kernel@xxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxxx; akpm@linux-
>> foundation.org; linux@xxxxxxxxxxx; lauraa@xxxxxxxxxxxxxx;
>> heiko.carstens@xxxxxxxxxx; d.kasatkin@xxxxxxxxxxx;
>> takahiro.akashi@xxxxxxxxxx; chris@xxxxxxxxxxxxxxxxxx; pebolle@xxxxxxxxxx; Liu,
>> Chuansheng; Zhang, Dongxing
>> Subject: Re: [PATCH] modify the IO_TLB_SEGSIZE to io_tlb_segsize
>> configurable as flexible requirement about SW-IOMMU.
>>
>> On Fri, Feb 06, 2015 at 07:01:14AM +0800, xiaomin1 wrote:
>>> The maximum of SW-IOMMU is limited to 2^11*128 = 256K.
>>> While in different platform and different requirements this seems improper.
>>> So modify the IO_TLB_SEGSIZE to io_tlb_segsize as configurable is make
>> sense.
>>
>> More details please. What is the issue you are hitting?
>>
> Example:
> If 1M bytes are requied. There has an error like.

Instead of allowing the bouncing of such large buffers, could the gadget
driver be modified to submit the buffers to the hardware in smaller chunks?

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/