Re: [RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

2022-06-23 Thread Tianyu Lan
On 6/22/2022 6:54 PM, Christoph Hellwig wrote: Thanks, this looks pretty good to me. A few comments below: Thanks for your review. On Fri, Jun 17, 2022 at 10:47:41AM -0400, Tianyu Lan wrote: +/** + * struct io_tlb_area - IO TLB memory area descriptor + * + * This is a single area with a

Re: [RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

2022-06-22 Thread Dongli Zhang
I will build the next RFC version of 64-bit swiotlb on top of this patch (or next version of this patch), so that it will render a more finalized view of 32-bt/64-bit plus multiple area. Thank you very much! Dongli Zhang On 6/22/22 3:54 AM, Christoph Hellwig wrote: > Thanks, > > this looks

Re: [RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

2022-06-22 Thread Christoph Hellwig
Thanks, this looks pretty good to me. A few comments below: On Fri, Jun 17, 2022 at 10:47:41AM -0400, Tianyu Lan wrote: > +/** > + * struct io_tlb_area - IO TLB memory area descriptor > + * > + * This is a single area with a single lock. > + * > + * @used:The number of used IO TLB block. >

[RFC PATCH V4 1/1] swiotlb: Split up single swiotlb lock

2022-06-17 Thread Tianyu Lan
From: Tianyu Lan Traditionally swiotlb was not performance critical because it was only used for slow devices. But in some setups, like TDX/SEV confidential guests, all IO has to go through swiotlb. Currently swiotlb only has a single lock. Under high IO load with multiple CPUs this can lead to