From: David Brownell <david-b@pacbell.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: Russ Dill <russ.dill@gmail.com>,
Artem Bityutskiy <dedekind@yandex.ru>,
David Hagood <david.hagood@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: Benchmarking: POP flash vs. MMC?
Date: Mon, 6 Apr 2009 03:48:34 -0700 [thread overview]
Message-ID: <200904060348.34996.david-b@pacbell.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0904060433000.22223@utopia.booyaka.com>
On Monday 06 April 2009, Paul Walmsley wrote:
> > Puzzle: get a dma_copypage() to work faster than copy_page().
> > Or a dma_clear_page() faster than clear_page(). Not easy...
>
> Doing it via the DMA engine may save power, since MPU can sleep.
But the CPU overhead of calling the DMA engine can exceed
that of the memcpy()/memset() ... ;)
Another concern is cache impact. In some cases, having the
dirty data in dcache is a big win. With DMA, the cache will
have been purged.
It'd be nice to see DMA versions of this stuff winning;
all I'm saying is that such wins are hard to achieve.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-06 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 21:24 Benchmarking: POP flash vs. MMC? david.hagood
2009-04-04 0:57 ` Russ Dill
2009-04-04 2:52 ` David Hagood
2009-04-04 4:16 ` Russ Dill
2009-04-05 22:53 ` David Brownell
2009-04-06 7:41 ` Artem Bityutskiy
2009-04-06 8:13 ` Russ Dill
2009-04-06 9:07 ` Artem Bityutskiy
2009-04-06 9:59 ` David Brownell
2009-04-06 10:08 ` Paul Walmsley
2009-04-06 10:23 ` David Brownell
2009-04-06 10:34 ` Paul Walmsley
2009-04-06 10:48 ` David Brownell [this message]
2009-04-07 17:22 ` Tony Lindgren
2009-04-07 12:09 ` Woodruff, Richard
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=200904060348.34996.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=david.hagood@gmail.com \
--cc=dedekind@yandex.ru \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=russ.dill@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 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.