On Mon, Feb 24, 2014 at 02:50:28PM -0600, Andy Gross wrote:
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
Hi folks,
Just wanted your thoughts/suggestions on how we can avoid overhead in the
EDMA
dmaengine driver. I am seeing a lots of performance drop specially for
On Mon, Feb 24, 2014 at 04:38:48PM -0600, Joel Fernandes wrote:
Actually I did do some tracing earlier before I posted this thread- and
notice there was excessive traces of locking/unlocking. It is very light
though as you pointed and lighter without debug options. The only other
notable
Hi folks,
Just wanted your thoughts/suggestions on how we can avoid overhead in the EDMA
dmaengine driver. I am seeing a lots of performance drop specially for small
transfers with EDMA versus before raw EDMA was moved to DMAEngine framework
(atleast 25%).
One of the things I am thinking about
Wrapping... (I've had to manually edit this.)
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
Just wanted your thoughts/suggestions on how we can avoid overhead in
the EDMA dmaengine driver. I am seeing a lots of performance drop
specially for small transfers with EDMA versus
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
Hi folks,
Just wanted your thoughts/suggestions on how we can avoid overhead in the EDMA
dmaengine driver. I am seeing a lots of performance drop specially for small
transfers with EDMA versus before raw EDMA was moved to
Hi Russell,
Firstly, thanks for your quick reply.
On 02/24/2014 01:21 PM, Russell King - ARM Linux wrote:
Wrapping... (I've had to manually edit this.)
On Mon, Feb 24, 2014 at 01:03:32PM -0600, Joel Fernandes wrote:
Just wanted your thoughts/suggestions on how we can avoid overhead in
the
Correcting myself from an earlier post..
On 02/24/2014 04:38 PM, Joel Fernandes wrote:
Also with respect to virt_dma (which is used by edma to manage all the
descriptors and lists) there are too many lists: submitted, issued,
completed etc and the descriptor moves from one to the other. I am
