linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'Chris Ball' <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	'Namjae Jeon' <linkinjeon@gmail.com>
Subject: RE: [PATCH v4 0/2] mmc: core: Support packed command feature of eMMC4.5
Date: Tue, 07 Feb 2012 17:40:00 +0900	[thread overview]
Message-ID: <001201cce574$14b7d220$3e277660$%jun@samsung.com> (raw)
In-Reply-To: <m2obte86qi.fsf@bob.laptop.org>

Hi Chris,

Chris Ball <cjb@laptop.org> wrote:
> Hi Seungwon,
> 
> On Thu, Jan 26 2012, Seungwon Jeon wrote:
> > This patch-set adds support of packed command feature
> > for eMMC4.5 devices.
> 
> Thanks, looks good!  Were you or Namjae able to measure any performance
> changes with this patchset applied?
We could get the difference results depending on eMMC device.
I have tested patch set with eMMC device which was not optimized in packed command.
In my environment there is a performance gain only with packed write
if total chunk size for transfer is large.
This is not common case in user scenario as of now.
Currently this patch set with regard to packed command is meaningful
and helpful for device supporting fully.

Best regards,
Seungwon Jeon.

> 
> - Chris.
> --
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> --
> 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

      reply	other threads:[~2012-02-07  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  9:04 [PATCH v4 0/2] mmc: core: Support packed command feature of eMMC4.5 Seungwon Jeon
2012-02-05  0:27 ` Chris Ball
2012-02-07  8:40   ` Seungwon Jeon [this message]

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='001201cce574$14b7d220$3e277660$%jun@samsung.com' \
    --to=tgih.jun@samsung.com \
    --cc=cjb@laptop.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).