From: Jaehoon Chung <jh80.chung@samsung.com>
To: Saugata Das <saugata.das@linaro.org>
Cc: Chris Ball <cjb@laptop.org>,
Saugata Das <saugata.das@stericsson.com>,
linux-mmc@vger.kernel.org
Subject: Re: [RFC] MMC-4.5 Context ID
Date: Mon, 06 Feb 2012 14:26:54 +0900 [thread overview]
Message-ID: <4F2F649E.2010106@samsung.com> (raw)
In-Reply-To: <CAKLKtzeRHVeMemTytmaon0GsZ2GqXwz_M_CX6aTj+xDDgN7HVg@mail.gmail.com>
On 02/06/2012 02:13 PM, Saugata Das wrote:
> On 5 February 2012 08:15, Chris Ball <cjb@laptop.org> wrote:
>> Hi,
>>
>> On Wed, Feb 01 2012, Saugata Das wrote:
>>> From: Saugata Das <saugata.das@linaro.org>
>>>
>>> This patch groups the read or write transfers to eMMC in different contexts
>>> based on the block number. Transfers to consecutive blocks are grouped to a
>>> common context. So several small transfers combine to give performance like
>>> a large multi block transfer.
>>>
>>> The patch creates a context of 1MB multiple in non-large unit mode. Reliable
>>> mode is enabled in the context based on whether reliable write is enabled.
>>
>> Do you see any performance changes with this patchset? If so, can you
>> give details?
>
> I do not see any performance impact (positive or negative) on the
> sample eMMC-4.5 device which I have. This could be due to the slow
> bridge which I use (1-bit mode at 25MHz) to connect the eMMC-4.5
> device on micro-SD slot of 8500 platform.
I think that should be increased the performance by how we select the context.
I also didn't see any performance benefit..8-bit mode at 50Mhz.
But i have interest for this feature
Best Regards,
Jaehoon Chung
>
>>
>> Thanks,
>>
>> - 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
> --
> 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:[~2012-02-06 5:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 15:27 [RFC] MMC-4.5 Context ID Saugata Das
2012-02-02 16:08 ` S, Venkatraman
2012-02-03 2:45 ` Jaehoon Chung
2012-02-03 5:48 ` Saugata Das
2012-02-03 5:47 ` Saugata Das
2012-02-05 2:45 ` Chris Ball
2012-02-06 5:13 ` Saugata Das
2012-02-06 5:26 ` Jaehoon Chung [this message]
2012-02-06 5:34 ` Saugata Das
2012-02-11 20:57 ` Chris Ball
2012-02-13 20:37 ` Saugata Das
2012-02-14 2:16 ` Jaehoon Chung
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=4F2F649E.2010106@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=saugata.das@linaro.org \
--cc=saugata.das@stericsson.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 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.