mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Greg KH <gregkh@linuxfoundation.org>, mzoran@crowfest.net
Cc: daniels@collabora.com, noralf@tronnes.org, popcornmix@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: vc04_services: Replace dmac_map_area with dmac_map_sg
Date: Mon, 24 Oct 2016 09:56:35 -0700	[thread overview]
Message-ID: <87bmy9sn24.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20161024132421.GB20116@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

Greg KH <gregkh@linuxfoundation.org> writes:

> On Sun, Oct 23, 2016 at 10:29:32PM -0700, mzoran@crowfest.net wrote:
>> From: Michael Zoran <mzoran@crowfest.net>
>> 
>> The original arm implementation uses dmac_map_area which is not
>> portable.  Replace it with an architecture neutral version
>> which uses dma_map_sg.
>> 
>> As you can see that for larger page sizes, the dma_map_sg
>> implementation is faster then the original unportable dma_map_area
>> implementation.  
>> 
>> Test                       dmac_map_area   dma_map_page dma_map_sg
>> vchiq_test -b 4 10000      51us/iter       76us/iter    76us
>> vchiq_test -b 8 10000      70us/iter       82us/iter    91us
>> vchiq_test -b 16 10000     94us/iter       118us/iter   121us
>> vchiq_test -b 32 10000     146us/iter      173us/iter   187us
>> vchiq_test -b 64 10000     263us/iter      328us/iter   299us
>> vchiq_test -b 128 10000    529us/iter      631us/iter   595us
>> vchiq_test -b 256 10000    2285us/iter     2275us/iter  2001us
>> vchiq_test -b 512 10000    4372us/iter     4616us/iter  4123us
>> 
>> For message sizes >= 64KB, dma_map_sg is faster then dma_map_page.
>> 
>> For message size >= 256KB, the dma_map_sg is the fastest
>> implementation.
>
> What is the "normal" message size value when using this driver?

For the contents of a bulk transfer, the performance case you care about
is moving an image (video decode, camera, etc.), so on the order of 1MB.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

  parent reply	other threads:[~2016-10-24 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24  5:29 mzoran
2016-10-24 13:24 ` Greg KH
2016-10-24 14:01   ` Michael Zoran
2016-10-24 16:56   ` Eric Anholt [this message]
2016-10-24 17:31 ` Eric Anholt
2016-10-25 15:00   ` Michael Zoran
2016-10-25 15:07     ` Michael Zoran
2016-10-25 16:16       ` Eric Anholt
2016-10-25 16:30         ` Michael Zoran

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=87bmy9sn24.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=daniels@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzoran@crowfest.net \
    --cc=noralf@tronnes.org \
    --cc=popcornmix@gmail.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

all inboxes | Powered by JetHome®