Re: [RFC 1/5] dmaengine: Add support for reporting DMA cached data amount

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09-10-18, 14:05, Peter Ujfalusi wrote:
> 
> 
> On 2018-10-09 13:47, Vinod wrote:
> > On 24-09-18, 16:00, Peter Ujfalusi wrote:
> >> A DMA hardware can have big cache or FIFO and the amount of data sitting in
> >> the DMA fabric can be an interest for the clients.
> >>
> >> For example in audio we want to know the delay in the data flow and in case
> >> the DMA have significantly large FIFO/cache, it can affect the latenc/delay
> > 
> > this looks okay to me, but not really up for 'cached', better
> > alternates?
> 
> It is after all the amount of bytes cached within the DMA fabric, but I
> agree it is a bit awkward.
> 
> Recently I tried to come up with something better, but did not went too
> far...
> dma_cached_bytes?
> dma_held_bytes?
> in_flight_bytes?
> not_in_source_but_not_yet_in_destination_bytes :D ?

yeah_that_sounds_good :D, i think in_flight would be apt here..
-- 
~Vinod



[Index of Archives]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux PCI]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux