From: Namjae Jeon <linkinjeon@gmail.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: Saugata Das <saugata.das@linaro.org>,
linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] mmc: core: Support packed command for eMMC4.5 device
Date: Thu, 26 Jan 2012 16:39:53 +0900 [thread overview]
Message-ID: <CAKYAXd8mKNGk2e8wo1eG9zB0L876HswMO4JmxAJ85TkouaB1UA@mail.gmail.com> (raw)
In-Reply-To: <000001ccdbfb$926d90b0$b748b210$%jun@samsung.com>
>> > - Add a variable member in mmc_host for minimum number of packed entries.
>> > This value can be overridden by host.
>> Ah.. Okay~ I clearly understand about two queston.
>> Totally, Looks good to me.
>> Thanks for your reply.
>> And I heard that packed cmd is not good while reading small chunk,
>> If so, I want to use packed write cmd not read cmd.
>> Can I use packed only packed write cmd by seperating
>> MMC_CAP2_PACKED_READ_CMD and MMC_CAP2_PACKED_WRITE_CMD ?
> Do you think this separate use is common?
> Let me consider this more.
It is just my idea on user side. if we can select packed read/write
set, I believe that we can optmize performance accoding to own's
environment.
Thanks.
next prev parent reply other threads:[~2012-01-26 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 4:06 [PATCH v3 2/2] mmc: core: Support packed command for eMMC4.5 device Seungwon Jeon
2012-01-23 10:03 ` Saugata Das
2012-01-24 22:54 ` Namjae Jeon
2012-01-25 5:18 ` Seungwon Jeon
2012-01-25 5:31 ` Namjae Jeon
2012-01-26 4:31 ` Namjae Jeon
2012-01-26 6:05 ` Seungwon Jeon
2012-01-26 6:42 ` Namjae Jeon
2012-01-26 7:24 ` Seungwon Jeon
2012-01-26 7:39 ` Namjae Jeon [this message]
2012-01-25 5:17 ` Seungwon Jeon
2012-01-26 20:52 ` Saugata Das
2012-01-27 6:55 ` Seungwon Jeon
2012-01-27 13:19 ` Saugata Das
2012-02-02 9:50 ` Seungwon Jeon
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=CAKYAXd8mKNGk2e8wo1eG9zB0L876HswMO4JmxAJ85TkouaB1UA@mail.gmail.com \
--to=linkinjeon@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=saugata.das@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).