From: Chris Ball <cjb@laptop.org>
To: merez@codeaurora.org
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
linux-mmc@vger.kernel.org,
'Subhash Jadavani' <subhashj@codeaurora.org>,
"'S, Venkatraman'" <svenkatr@ti.com>,
'Saugata Das' <saugata.das@linaro.org>,
'Namjae Jeon' <linkinjeon@gmail.com>
Subject: Re: [PATCH v8 1/2] mmc: add packed command feature of eMMC4.5
Date: Tue, 10 Jul 2012 03:33:55 -0400 [thread overview]
Message-ID: <87mx38qdcs.fsf@octavius.laptop.org> (raw)
In-Reply-To: <fc0bbbfabb899fd68e522b843b668041.squirrel@www.codeaurora.org> (merez@codeaurora.org's message of "Mon, 9 Jul 2012 23:23:52 -0700 (PDT)")
Hi,
On Tue, Jul 10 2012, merez@codeaurora.org wrote:
>> Sorry, I don't have a copy of the eMMC 4.5 spec -- is PACKED_EVENT_EN
>> a one-time programmable fuse on the eMMC, like BKOPS_ENABLE was?
>
> No, it's not.
Excellent, thanks.
I've pushed both v8 patches to mmc-next. Before pushing it up to Linus,
I'd like to get a better idea of the variety of performances differences
seen using packed writes -- has it been tried on devices from multiple
eMMC vendors, and multiple host controller vendors? Can we try to build
up a quick table of results, with a standard test like iozone, to check
that we've got decent test coverage? Seungwon suggests using:
iozone -az -i0 -I -s 10m -f /target/test -e
I'm also worried about how much code this is adding, but I agree that
it's worth it if the performance benefits are as described.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-07-10 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 4:32 [PATCH v8 1/2] mmc: add packed command feature of eMMC4.5 Seungwon Jeon
2012-07-10 5:42 ` merez
2012-07-10 5:54 ` Chris Ball
2012-07-10 6:23 ` merez
2012-07-10 7:33 ` Chris Ball [this message]
2012-07-10 10:45 ` merez
2012-07-10 6:24 ` S, Venkatraman
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=87mx38qdcs.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=linkinjeon@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=merez@codeaurora.org \
--cc=saugata.das@linaro.org \
--cc=subhashj@codeaurora.org \
--cc=svenkatr@ti.com \
--cc=tgih.jun@samsung.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