From: Chris Ball <cjb@laptop.org>
To: Per Forlin <per.forlin@linaro.org>
Cc: linaro-dev@lists.linaro.org,
Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, "S,
Venkatraman" <svenkatr@ti.com>
Subject: Re: [PATCH v9 00/12] use nonblock mmc requests to minimize latency
Date: Sat, 09 Jul 2011 18:09:45 -0400 [thread overview]
Message-ID: <m2y607jec6.fsf@bob.laptop.org> (raw)
In-Reply-To: <1309539333-2606-1-git-send-email-per.forlin@linaro.org> (Per Forlin's message of "Fri, 1 Jul 2011 18:55:21 +0200")
Hi Per,
On Fri, Jul 01 2011, Per Forlin wrote:
> How significant is the cache maintenance over head?
> It depends, the eMMC are much faster now
> compared to a few years ago and cache maintenance cost more due to
> multiple cache levels and speculative cache pre-fetch. In relation the
> cost for handling the caches have increased and is now a bottle neck
> dealing with fast eMMC together with DMA.
Thanks very much, I've pushed v9 of the patchset to mmc-next for 3.1
(after fixing some merge conflicts against Adrian Hunter's recent patches
and rewording some of the commit message texts).
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-09 22:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 16:55 [PATCH v9 00/12] use nonblock mmc requests to minimize latency Per Forlin
[not found] ` <1309539333-2606-1-git-send-email-per.forlin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-01 16:55 ` [PATCH v9 01/12] mmc: core: add non-blocking mmc request function Per Forlin
2011-07-01 16:55 ` [PATCH v9 02/12] omap_hsmmc: add support for pre_req and post_req Per Forlin
2011-07-01 16:55 ` [PATCH v9 03/12] mmci: implement pre_req() and post_req() Per Forlin
2011-07-01 16:55 ` [PATCH v9 04/12] mmc: mmc_test: add debugfs file to list all tests Per Forlin
2011-07-01 16:55 ` [PATCH v9 05/12] mmc: mmc_test: add test for non-blocking transfers Per Forlin
2011-07-01 16:55 ` [PATCH v9 06/12] mmc: mmc_test: test to measure how sg_len affect performance Per Forlin
2011-07-01 16:55 ` [PATCH v9 07/12] mmc: block: add member in mmc queue struct to hold request data Per Forlin
2011-07-01 16:55 ` [PATCH v9 08/12] mmc: block: add a block request prepare function Per Forlin
2011-07-01 16:55 ` [PATCH v9 09/12] mmc: block: move error code in issue_rw_rq to a separate function Per Forlin
2011-07-01 16:55 ` [PATCH v9 10/12] mmc: queue: add a second mmc queue request member Per Forlin
2011-07-01 16:55 ` [PATCH v9 11/12] mmc: core: add random fault injection Per Forlin
2011-07-19 6:17 ` Per Forlin
2011-07-01 16:55 ` [PATCH v9 12/12] mmc: block: add handling for two parallel block requests in issue_rw_rq Per Forlin
2011-07-09 22:09 ` Chris Ball [this message]
2011-08-26 16:19 ` [PATCH v9 00/12] use nonblock mmc requests to minimize latency Russell King - ARM Linux
2011-08-26 16:28 ` Santosh
2011-08-28 10:50 ` Per Forlin
2011-08-28 11:11 ` Russell King - ARM Linux
2011-08-28 12:13 ` Per Forlin
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=m2y607jec6.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=per.forlin@linaro.org \
--cc=svenkatr@ti.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