From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] dmaengine: virt-dma: fix completion list manipulation
Date: Tue, 03 Mar 2015 12:55:07 +0100 [thread overview]
Message-ID: <87zj7uz46c.fsf@free.fr> (raw)
In-Reply-To: <54F5992E.3060808@metafoo.de> (Lars-Peter Clausen's message of "Tue, 03 Mar 2015 12:21:18 +0100")
Lars-Peter Clausen <lars@metafoo.de> writes:
> On 03/03/2015 11:27 AM, Robert Jarzmik wrote:
>> I still think that their use of virt-dma is incorrect, ie. that at one point in
>> time a virtual descriptor has to be on exactly one list of virt-dma (excepting
>> transient critical sections).
>
> Well the drivers conform to the current expected behavior. It might be worth
> changing that, but you need to modify all the driver to conform to the new
> semantics, rather than just changing the API.
>
> Requiring that the descriptor is always on one of the virt-dma list is to
> restrictive. Some DMA controllers are able to submit multiple descriptors at the
> same time, these typically have a separate list to manage to active
> descriptors.
Ah, so your understanding of the virt-dma API is that the virtual descriptors
might be out of virt-dma linked lists. In that case, I must rethink this over,
as I was thinking the "multiple active descriptors" case was relying on all
these descriptors being on the desc_issued list, and the "multiple simultaneous
active" list was not in virtual descriptor but in the dmaengine driver's one.
Anyway, I'll drop this patch for now, as nobody else seems to care about
virt-dma semantics, and I won't modify the API if the pros and cons I see do
look equivalent (which is the case right now).
Cheers.
--
Robert
prev parent reply other threads:[~2015-03-03 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 21:19 [PATCH] dmaengine: virt-dma: fix completion list manipulation Robert Jarzmik
2015-03-02 21:29 ` Lars-Peter Clausen
2015-03-02 22:03 ` Robert Jarzmik
2015-03-03 7:23 ` Lars-Peter Clausen
2015-03-03 10:27 ` Robert Jarzmik
2015-03-03 11:21 ` Lars-Peter Clausen
2015-03-03 11:55 ` Robert Jarzmik [this message]
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=87zj7uz46c.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=vinod.koul@intel.com \
/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