From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] dmaengine: virt-dma: don't always free descriptor upon completion
Date: Thu, 29 Oct 2015 10:54:13 +0900 [thread overview]
Message-ID: <20151029015411.GD18368@vkoul-mobl.iind.intel.com> (raw)
In-Reply-To: <87oafowahl.fsf@belgarion.home>
On Sat, Oct 24, 2015 at 11:57:53AM +0200, Robert Jarzmik wrote:
> Robert Jarzmik <robert.jarzmik@free.fr> writes:
>
> > This patch attempts to enhance the case of a transfer submitted multiple
> > times, and where the cost of creating the descriptors chain is not
> > negligible.
> >
> > This happens with big video buffers (several megabytes, ie. several
> > thousands of linked descriptors in one scatter-gather list). In these
> > cases, a video driver would want to do :
> > - tx = dmaengine_prep_slave_sg()
> > - dma_engine_submit(tx);
> > - dma_async_issue_pending()
> > - wait for video completion
> > - read video data (or not, skipping a frame is also possible)
> > - dma_engine_submit(tx)
> > => here, the descriptors chain recalculation will take time
> > => the dma coherent allocation over and over might create holes in
> > the dma pool, which is counter-productive.
> > - dma_async_issue_pending()
> > - etc ...
> >
> > In order to cope with this case, virt-dma is modified to prevent freeing
> > the descriptors upon completion if DMA_CTRL_REUSE flag is set in the
> > transfer.
> >
> > This patch is a respin of the former DMA_CTRL_ACK approach, which was
> > reverted due to a regression in audio drivers.
> >
> > Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> > ---
> > Since v1: added doxygen commit to vchan_tx_desc_free
>
> Hi Vinod,
>
> Is this serie good for you or do you have remaining comments to be addressed ?
Hi Robert,
This series looks good, but I am afraid we are very close to merge window I
would like this to be deffered to next one for more stabililty tests and
coverage
I have pushed this to topic/test/desc_reuse now.
This will be in -next after merge window
Thanks for fixing this up
--
~Vinod
next prev parent reply other threads:[~2015-10-29 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 19:54 [PATCH v2 1/3] dmaengine: virt-dma: don't always free descriptor upon completion Robert Jarzmik
2015-10-13 19:54 ` [PATCH v2 2/3] dmaengine: enable DMA_CTRL_REUSE Robert Jarzmik
2015-10-13 19:54 ` [PATCH v2 3/3] dmaengine: pxa_dma: declare transfer are reusable Robert Jarzmik
2015-10-24 9:57 ` [PATCH v2 1/3] dmaengine: virt-dma: don't always free descriptor upon completion Robert Jarzmik
2015-10-29 1:54 ` Vinod Koul [this message]
2015-10-29 6:28 ` Robert Jarzmik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151029015411.GD18368@vkoul-mobl.iind.intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox