[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e05e25e-e569-402e-d81b-8ac2cff1c0e8@arm.com>
Date: Tue, 3 Aug 2021 11:53:45 +0100
From: Robin Murphy <robin.murphy@....com>
To: Yongji Xie <xieyongji@...edance.com>,
Jason Wang <jasowang@...hat.com>
Cc: kvm <kvm@...r.kernel.org>, "Michael S. Tsirkin" <mst@...hat.com>,
virtualization <virtualization@...ts.linux-foundation.org>,
Christian Brauner <christian.brauner@...onical.com>,
Jonathan Corbet <corbet@....net>,
Matthew Wilcox <willy@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Stefano Garzarella <sgarzare@...hat.com>,
Liu Xiaodong <xiaodong.liu@...el.com>,
linux-fsdevel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>,
Stefan Hajnoczi <stefanha@...hat.com>,
songmuchun@...edance.com, Jens Axboe <axboe@...nel.dk>,
He Zhe <zhe.he@...driver.com>,
Greg KH <gregkh@...uxfoundation.org>,
Randy Dunlap <rdunlap@...radead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
iommu@...ts.linux-foundation.org, bcrl@...ck.org,
netdev@...r.kernel.org, Joe Perches <joe@...ches.com>,
Mika Penttilä <mika.penttila@...tfour.com>
Subject: Re: [PATCH v10 01/17] iova: Export alloc_iova_fast() and
free_iova_fast()
On 2021-08-03 09:54, Yongji Xie wrote:
> On Tue, Aug 3, 2021 at 3:41 PM Jason Wang <jasowang@...hat.com> wrote:
>>
>>
>> 在 2021/7/29 下午3:34, Xie Yongji 写道:
>>> Export alloc_iova_fast() and free_iova_fast() so that
>>> some modules can use it to improve iova allocation efficiency.
>>
>>
>> It's better to explain why alloc_iova() is not sufficient here.
>>
>
> Fine.
What I fail to understand from the later patches is what the IOVA domain
actually represents. If the "device" is a userspace process then
logically the "IOVA" would be the userspace address, so presumably
somewhere you're having to translate between this arbitrary address
space and actual usable addresses - if you're worried about efficiency
surely it would be even better to not do that?
Presumably userspace doesn't have any concern about alignment and the
things we have to worry about for the DMA API in general, so it's pretty
much just allocating slots in a buffer, and there are far more effective
ways to do that than a full-blown address space manager. If you're going
to reuse any infrastructure I'd have expected it to be SWIOTLB rather
than the IOVA allocator. Because, y'know, you're *literally implementing
a software I/O TLB* ;)
Robin.
Powered by blists - more mailing lists