From: Praveen G K <praveen.gk@gmail.com>
To: "Andrei E. Warkentin" <andrey.warkentin@gmail.com>
Cc: "J Freyensee" <james_p_freyensee@linux.intel.com>,
"Andrei Warkentin" <awarkentin@vmware.com>,
"Per Förlin" <per.forlin@stericsson.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
linux-mmc@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Jon Medhurst" <tixy@linaro.org>
Subject: Re: slow eMMC write speed
Date: Thu, 20 Oct 2011 08:10:02 -0700 [thread overview]
Message-ID: <CAHzg1A-E0ziGaO_4ttm6tWBsLZe+cUVt=Cn7Cr8gwC0XA_PSSw@mail.gmail.com> (raw)
In-Reply-To: <CANz0V+48-8wXLjN4=LsU=-iQjLsgczqYo0Vs8xF=0Y=dCG=o=Q@mail.gmail.com>
2011/10/20 Andrei E. Warkentin <andrey.warkentin@gmail.com>:
> 2011/10/19 Praveen G K <praveen.gk@gmail.com>:
>> Also, can somebody please tell me the significance of blk_end_request? Thanks.
>> Why do we call this after every block read or write?
>
> Because you want to update the struct request with the amount
> written/read. If the entire
> requested I/O range has been satiffied, blk_end_request also calls
> blk_finish_request and
> completes the request.
Just for a quick understanding, I did the following
During every eMMC write, I called the multi block write command with
the same set of data, and I called the mmc_end_request after let's
say every 10 transfers (with each transfer being 128 blocks). I
noticed that I did not see those big busy wait times as frequently as
compared to calling blk_end_request after every 128 block was
transferred. Why is that happening?
> I/O is asynchronous - hence, you need to let whatever made the request
> know it's completed.
So, does that mean, the actual writes to the eMMC (or reads from the
eMMC) takes place here? If so, what happens when we send the MULTI
BLOCK WRITE command?
> A
>
next prev parent reply other threads:[~2011-10-20 15:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 5:05 slow eMMC write speed Praveen G K
2011-09-28 5:42 ` 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 [this message]
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='CAHzg1A-E0ziGaO_4ttm6tWBsLZe+cUVt=Cn7Cr8gwC0XA_PSSw@mail.gmail.com' \
--to=praveen.gk@gmail.com \
--cc=andrey.warkentin@gmail.com \
--cc=arnd@arndb.de \
--cc=awarkentin@vmware.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=tixy@linaro.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.