lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 3 Aug 2021 11:53:45 +0100
From:   Robin Murphy <>
To:     Yongji Xie <>,
        Jason Wang <>
Cc:     kvm <>, "Michael S. Tsirkin" <>,
        virtualization <>,
        Christian Brauner <>,
        Jonathan Corbet <>,
        Matthew Wilcox <>,
        Christoph Hellwig <>,
        Dan Carpenter <>,
        Stefano Garzarella <>,
        Liu Xiaodong <>,, Al Viro <>,
        Stefan Hajnoczi <>,, Jens Axboe <>,
        He Zhe <>,
        Greg KH <>,
        Randy Dunlap <>,
        linux-kernel <>,,,, Joe Perches <>,
        Mika Penttilä <>
Subject: Re: [PATCH v10 01/17] iova: Export alloc_iova_fast() and

On 2021-08-03 09:54, Yongji Xie wrote:
> On Tue, Aug 3, 2021 at 3:41 PM Jason Wang <> 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* ;)


Powered by blists - more mailing lists