From: Chris Ball <chris@printf.net>
To: Apelete Seketeli <apelete@seketeli.net>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
Alex Smith <alex.smith@imgtec.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] mmc: jz4740: prepare next dma transfer in parallel with current transfer
Date: Tue, 12 Aug 2014 19:12:33 +0100 [thread overview]
Message-ID: <86y4ut60ha.fsf@void.printf.net> (raw)
In-Reply-To: <1405917465-18185-3-git-send-email-apelete@seketeli.net> (Apelete Seketeli's message of "Mon, 21 Jul 2014 06:37:45 +0200")
Hi Apelete,
On Mon, Jul 21 2014, Apelete Seketeli wrote:
> It should help reduce the impact of DMA preparation overhead on the SD
> card performance.
Did you do any benchmarking to check that this is true? (If so, it'd
be good to note what performance change you saw in the commit message.)
Thanks!
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-08-12 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 4:37 [PATCH v6 0/2] Use DMA for data transfers in JZ4740 MMC driver Apelete Seketeli
2014-07-21 4:37 ` [PATCH v6 1/2] mmc: jz4740: add dma infrastructure for data transfers Apelete Seketeli
2014-08-12 16:21 ` Ulf Hansson
2014-07-21 4:37 ` [PATCH v6 2/2] mmc: jz4740: prepare next dma transfer in parallel with current transfer Apelete Seketeli
2014-08-12 16:22 ` Ulf Hansson
2014-08-12 18:10 ` Apelete Seketeli
2014-08-12 20:15 ` Ulf Hansson
2014-08-12 18:12 ` Chris Ball [this message]
2014-08-12 20:02 ` Apelete Seketeli
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=86y4ut60ha.fsf@void.printf.net \
--to=chris@printf.net \
--cc=alex.smith@imgtec.com \
--cc=apelete@seketeli.net \
--cc=hsweeten@visionengravers.com \
--cc=lars@metafoo.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yongjun_wei@trendmicro.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.