Re: Poor performace on mmap reading arm64 on audio device

[Takashi Iwai <tiwai@suse.de>]

On Sat, 21 Nov 2020 10:40:04 +0100,
Michael Nazzareno Trimarchi wrote:
> 
> Hi all
> 
> I'm trying to figure out how to increase performance on audio reading
> using the mmap interface. Right now what I understand it's that
> allocation comes from core/memalloc.c ops that allocate the memory for
> dma under driver/dma.
> The reference platform I have is an imx8mm and the allocation in arm64 is:
> 
> 0xffff800011ff5000-0xffff800012005000          64K PTE       RW NX SHD
> AF            UXN MEM/NORMAL-NC
> 
> This is the reason that is allocated for dma interface.
> 
> Now access linear on the multichannel interface the performance is bad
> but worse if I try to access a channel a time on read.
> So it looks like it is better to copy the block using memcpy on a
> cached area and then operate on a single channel sample. If it's
> correct what I'm saying the mmap_begin and mmap_commit
> basically they don't do anything on cache level so the page mapping
> and way is used is always the same. Can the interface be modified to
> allow cache the area during read and restore in the commit
> phase?

The current API of the mmap for the sound ring-buffer is designed to
allow concurrent accesses at any time in the minimalistic kernel-user
context switching.  So the whole buffer is allocated as coherent and
mmapped in a shot.  It's pretty efficient for architectures like x86,
but has disadvantages on ARM, indeed.

The mmap_begin and mmap_commit are the concepts in the alsa-lib side
for supporting the plugins better, and they doesn't represent kernel
ABI.  So, this extension would be needed at first, and the memory
allocation mechanism has to be changed as well.  Last but not least,
the concurrency has to be reconsidered if this approach is taken.

That said, it's possible in theory, but practically no trivial task.


thanks,

Takashi