From: Praveen G K <praveen.gk@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: slow eMMC write speed
Date: Thu, 22 Sep 2011 22:05:51 -0700 [thread overview]
Message-ID: <CAHzg1A9usWP8o3xjEq3yFn56bEqk_Qp0a8-2FJzoRZG1MqPRPA@mail.gmail.com> (raw)
Hello all,
I am working on the block driver module of the eMMC driver (SDIO 3.0
controller). I am seeing very low write speed for eMMC transfers. On
further debugging, I observed that every 63rd and 64th transfer takes
a long time. I have tabulated this by noting the time interval
between when CMD 25 (multi block write command) is sent and when
DATA_END interrupt is received. In normal cases, to transfer 64k (128
blocks of data), it takes about 2.5ms. But, under the really slow
transfer speed cases, it takes about 250-350ms to get the data_end
interrupt after the multiblock write command is sent. In some cases,
it takes a longer time. This radically reduces the throughput of the
transfers.
I have also enabled the bounce buffers. As a side question, can
somebody please tell me why the bounce buffer is restricted to 64kB?
Thanks in advance for any help that you can provide me on this issue.
Also, please include my email id in the cc field when replying to this
email since I am not subscribed to this mailing list.
Thanks,
Praveen Krishnan
next reply other threads:[~2011-09-23 5:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 5:05 Praveen G K [this message]
2011-09-28 5:42 ` slow eMMC write speed Linus Walleij
2011-09-28 19:06 ` Praveen G K
2011-09-28 19:59 ` J Freyensee
2011-09-28 20:34 ` Praveen G K
2011-09-28 21:01 ` J Freyensee
2011-09-28 21:03 ` Praveen G K
2011-09-28 21:34 ` J Freyensee
2011-09-28 22:24 ` Praveen G K
2011-09-28 22:59 ` J Freyensee
2011-09-28 23:16 ` Praveen G K
2011-09-29 0:57 ` Philip Rakity
2011-09-29 2:24 ` Praveen G K
2011-09-29 3:30 ` Philip Rakity
2011-09-29 7:24 ` Linus Walleij
2011-09-29 8:17 ` Per Förlin
2011-09-29 20:16 ` J Freyensee
2011-09-30 8:22 ` Andrei E. Warkentin
2011-10-01 0:33 ` J Freyensee
2011-10-02 6:20 ` Andrei E. Warkentin
2011-10-03 18:01 ` J Freyensee
2011-10-03 20:19 ` Andrei Warkentin
2011-10-03 21:00 ` J Freyensee
2011-10-04 7:59 ` Andrei E. Warkentin
2011-10-19 23:27 ` Praveen G K
2011-10-20 15:01 ` Andrei E. Warkentin
2011-10-20 15:10 ` Praveen G K
2011-10-20 15:26 ` Andrei Warkentin
2011-10-20 16:07 ` Praveen G K
2011-10-21 4:45 ` Andrei E. Warkentin
2011-09-29 7:05 ` Linus Walleij
2011-09-29 7:33 ` Linus Walleij
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=CAHzg1A9usWP8o3xjEq3yFn56bEqk_Qp0a8-2FJzoRZG1MqPRPA@mail.gmail.com \
--to=praveen.gk@gmail.com \
--cc=linux-mmc@vger.kernel.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 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.