From: merez@codeaurora.org
To: "Seungwon Jeon" <tgih.jun@samsung.com>
Cc: merez@codeaurora.org, "'Namjae Jeon'" <linkinjeon@gmail.com>,
linux-mmc@vger.kernel.org, "'Chris Ball'" <cjb@laptop.org>,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH v5 2/2] mmc: core: Support packed command for eMMC4.5 device
Date: Sun, 11 Mar 2012 14:36:54 -0700 (PDT) [thread overview]
Message-ID: <dbfd894b689405f525e17aa5373a2602.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <000001ccfbf7$ac3e7510$04bb5f30$%jun@samsung.com>
> Maya Erez <merez@codeaurora.org> wrote:
>> > Hi. Merez.
>> >
>> > Thanks a lot about your performance measurement.
>> >
>> > I think that your measurement is enough and correct and the firmware
>> > of mmc vender should be optimized or change properly rather than
>> > modifying the current patch.
>> >
>> > And currently we can use only write packed cmd by my suggestion.
>> >
>> > I would like to add my reviewd-by tag in updated patches also.
>> >
>> > Reviewed-by: Namjae Jeon <linkinjeon@gmail.com>
>> >
>> > Thanks.
>>
>> I tend to disagree. Adding a massive amount of code that would be
>> disabled
>> can be risky. In case this code will not be in use it will not be
>> properly
>> tested and its reliability will be uncertain.
>>
> If you found something to be correct, please let me know that.
> It would be rightly appreciated.
>
> Best regards,
> Seungwon Jeon.
Hi Jeon,
The write packing code looks good to me.
However, the separation of read and write packing to different patches is
very important to us.
As I specified before, we decided to enable only the write packing. We
plan to thoroughly test the write packing (edge cases and error handling)
and will not test the read packing. Therefore we would like to have the
ability to get only the write packing code.
In my previous comment I talked about the risk of mainlining a dead
code. Every feature that is integrated is considered to be fully tested
and in the future it might be enabled, assuming that is was already
tested.
Can you please specify how you tested the read and write packing? Did you
perform edge cases and error handling tests? Do you have test code that
can be shared?
Thanks,
Maya Erez
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-03-11 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 18:10 merez
2012-03-01 7:47 ` Namjae Jeon
2012-03-02 14:26 ` merez
2012-03-04 8:09 ` Saugata Das
2012-03-05 5:21 ` merez
2012-03-04 8:25 ` Namjae Jeon
2012-03-06 14:10 ` merez
2012-03-07 0:17 ` Seungwon Jeon
2012-03-11 21:36 ` merez [this message]
2012-03-13 0:47 ` Seungwon Jeon
2012-03-17 14:59 ` merez
2012-03-01 9:01 ` Saugata Das
2012-03-02 0:09 ` Seungwon Jeon
-- strict thread matches above, loose matches on Subject: below --
2012-04-26 12:21 merez
2012-04-30 0:31 ` Seungwon Jeon
2012-05-02 18:35 ` merez
2012-05-08 23:41 ` Seungwon Jeon
2012-02-27 10:20 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=dbfd894b689405f525e17aa5373a2602.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=cjb@laptop.org \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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
Powered by JetHome