From: "Matwey V. Kornilov" <matwey@sai.msu.ru>
To: hverkuil@xs4all.nl, mchehab@kernel.org
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
rostedt@goodmis.org, mingo@redhat.com, isely@pobox.com,
bhumirks@gmail.com, colin.king@canonical.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
ezequiel@collabora.com, laurent.pinchart@ideasonboard.com
Subject: [PATCH v2 2/2] media: usb: pwc: Don't use coherent DMA buffers for ISO transfer
Date: Fri, 22 Jun 2018 15:04:19 +0300 [thread overview]
Message-ID: <20180622120419.7675-3-matwey@sai.msu.ru> (raw)
In-Reply-To: <20180622120419.7675-1-matwey@sai.msu.ru>
DMA cocherency slows the transfer down on systems without hardware
coherent DMA.
Based on previous commit the following performance benchmarks have been
carried out. Average memcpy() data transfer rate (rate) and handler
completion time (time) have been measured when running video stream at
640x480 resolution at 10fps.
x86_64 based system (Intel Core i5-3470). This platform has hardware
coherent DMA support and proposed change doesn't make big difference here.
* kmalloc: rate = (4.4 +- 1.0) GBps
time = (2.4 +- 1.2) usec
* usb_alloc_coherent: rate = (4.1 +- 0.9) GBps
time = (2.5 +- 1.0) usec
We see that the measurements agree well within error ranges in this case.
So no performance downgrade is introduced.
armv7l based system (TI AM335x BeagleBone Black). This platform has no
hardware coherent DMA support. DMA coherence is implemented via disabled
page caching that slows down memcpy() due to memory controller behaviour.
* kmalloc: rate = (190 +- 30) MBps
time = (50 +- 10) usec
* usb_alloc_coherent: rate = (33 +- 4) MBps
time = (3000 +- 400) usec
Note, that quantative difference leads (this commit leads to 5 times
acceleration) to qualitative behavior change in this case. As it was
stated before, the video stream can not be successfully received at AM335x
platforms with MUSB based USB host controller due to performance issues
[1].
[1] https://www.spinics.net/lists/linux-usb/msg165735.html
Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
---
drivers/media/usb/pwc/pwc-if.c | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/media/usb/pwc/pwc-if.c b/drivers/media/usb/pwc/pwc-if.c
index 72d2897a4b9f..339a285600d1 100644
--- a/drivers/media/usb/pwc/pwc-if.c
+++ b/drivers/media/usb/pwc/pwc-if.c
@@ -427,11 +427,8 @@ static int pwc_isoc_init(struct pwc_device *pdev)
urb->interval = 1; // devik
urb->dev = udev;
urb->pipe = usb_rcvisocpipe(udev, pdev->vendpoint);
- urb->transfer_flags = URB_ISO_ASAP | URB_NO_TRANSFER_DMA_MAP;
- urb->transfer_buffer = usb_alloc_coherent(udev,
- ISO_BUFFER_SIZE,
- GFP_KERNEL,
- &urb->transfer_dma);
+ urb->transfer_flags = URB_ISO_ASAP;
+ urb->transfer_buffer = kmalloc(ISO_BUFFER_SIZE, GFP_KERNEL);
if (urb->transfer_buffer == NULL) {
PWC_ERROR("Failed to allocate urb buffer %d\n", i);
pwc_isoc_cleanup(pdev);
@@ -491,10 +488,7 @@ static void pwc_iso_free(struct pwc_device *pdev)
if (pdev->urbs[i]) {
PWC_DEBUG_MEMORY("Freeing URB\n");
if (pdev->urbs[i]->transfer_buffer) {
- usb_free_coherent(pdev->udev,
- pdev->urbs[i]->transfer_buffer_length,
- pdev->urbs[i]->transfer_buffer,
- pdev->urbs[i]->transfer_dma);
+ kfree(pdev->urbs[i]->transfer_buffer);
}
usb_free_urb(pdev->urbs[i]);
pdev->urbs[i] = NULL;
--
2.16.4
next prev parent reply other threads:[~2018-06-22 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:04 [PATCH v2 0/2] " Matwey V. Kornilov
2018-06-22 12:04 ` [PATCH v2 1/2] media: usb: pwc: Introduce TRACE_EVENTs for pwc_isoc_handler() Matwey V. Kornilov
2018-06-22 15:52 ` Steven Rostedt
2018-06-22 12:04 ` Matwey V. Kornilov [this message]
2018-07-13 16:11 ` [PATCH v2 2/2] media: usb: pwc: Don't use coherent DMA buffers for ISO transfer Matwey V. Kornilov
2018-08-08 22:46 ` Laurent Pinchart
2018-08-09 9:18 ` Matwey V. Kornilov
2018-08-09 9:44 ` Laurent Pinchart
2018-08-09 14:30 ` Tomasz Figa
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=20180622120419.7675-3-matwey@sai.msu.ru \
--to=matwey@sai.msu.ru \
--cc=bhumirks@gmail.com \
--cc=colin.king@canonical.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=isely@pobox.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®