From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'Arnd Bergmann' <arnd.bergmann@linaro.org>,
'Chris Ball' <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, 'Maya Erez' <merez@codeaurora.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 v9 0/2] mmc: support packed command feature of eMMC4.5
Date: Tue, 12 Feb 2013 19:53:31 +0900 [thread overview]
Message-ID: <001f01ce090f$329c3320$97d49960$%jun@samsung.com> (raw)
In-Reply-To: <201302112007.10195.arnd.bergmann@linaro.org>
On Tuesday, February 12, 2013, Arnd Bergmann wrote:
> On Monday 11 February 2013, Chris Ball wrote:
> > On Wed, Feb 06 2013, Seungwon Jeon wrote:
> > > This patch-set adds support of packed command feature for eMMC4.5 devices.
> > > Specially, packed write is introduced.
> >
> > Thanks, I've pushed this to mmc-next for 3.9 now.
> >
> > It would be great to see benchmarks for the effect on average write
> > latency, instead of just throughput, though.
>
> Yes, I agree absolutely. In the end, it's always the latency that
> matters for user experience not the maximum throughput.
I didn't see a significant difference in random I/O.
Write packing completely depends on seamless I/O from block layer.
As size of media contents is bigger, enhanced write is required in some user scenarios.
I guess write throughput is important factor cannot be easily ignored.
Thanks,
Seungwon Jeon
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" 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:[~2013-02-12 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 8:00 [PATCH v9 0/2] mmc: support packed command feature of eMMC4.5 Seungwon Jeon
2013-02-08 19:24 ` merez
2013-02-11 18:12 ` Chris Ball
2013-02-11 20:07 ` Arnd Bergmann
2013-02-12 10:53 ` Seungwon Jeon [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-08 19:22 merez
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='001f01ce090f$329c3320$97d49960$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=arnd.bergmann@linaro.org \
--cc=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 \
/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