Dear David > -----Original Message----- > From: David Vrabel [mailto:[email protected]] > Sent: Tuesday, February 10, 2015 5:46 PM > To: Wang, Xiaoming; Konrad Rzeszutek Wilk > Cc: [email protected]; [email protected]; Zhang, Dongxing; > [email protected]; [email protected]; > [email protected]; [email protected]; ralf@linux- > mips.org; [email protected]; [email protected]; > [email protected]; [email protected]; xen- > [email protected]; [email protected]; Liu, Chuansheng; > [email protected] > Subject: Re: [Xen-devel] [PATCH] modify the IO_TLB_SEGSIZE to > io_tlb_segsize configurable as flexible requirement about SW-IOMMU. > > On 06/02/15 00:10, Wang, Xiaoming wrote: > > > > > >> -----Original Message----- > >> From: Konrad Rzeszutek Wilk [mailto:[email protected]] > >> Sent: Friday, February 6, 2015 3:33 AM > >> To: Wang, Xiaoming > >> Cc: [email protected]; [email protected]; > >> [email protected]; [email protected]; linux- > >> [email protected]; [email protected]; akpm@linux- > >> foundation.org; [email protected]; [email protected]; > >> [email protected]; [email protected]; > >> [email protected]; [email protected]; > >> [email protected]; 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
Our target is try to make IO_TLB_SEGSIZE configurable. Neither 256 bytes or 1M bytes seems suitable value, I think. It's better to use the tactics something like kmem_cache_create in kmalloc function. But SW-IOMMU seems more lighter. So we choose variable rather than function. Xiaoming. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
