From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753555Ab2CKVhA (ORCPT ); Sun, 11 Mar 2012 17:37:00 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:52015 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518Ab2CKVgy (ORCPT ); Sun, 11 Mar 2012 17:36:54 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6646"; a="169189790" Message-ID: In-Reply-To: <000001ccfbf7$ac3e7510$04bb5f30$%jun@samsung.com> References: <4934441a17d25c3249556f7bf281b1be.squirrel@www.codeaurora.org> <6669559e86c1d13b27e941ff2acf89d2.squirrel@www.codeaurora.org> <000001ccfbf7$ac3e7510$04bb5f30$%jun@samsung.com> Date: Sun, 11 Mar 2012 14:36:54 -0700 (PDT) Subject: RE: [PATCH v5 2/2] mmc: core: Support packed command for eMMC4.5 device From: merez@codeaurora.org To: "Seungwon Jeon" Cc: merez@codeaurora.org, "'Namjae Jeon'" , linux-mmc@vger.kernel.org, "'Chris Ball'" , linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Maya Erez 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 >> > >> > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: merez@codeaurora.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) Message-ID: References: <4934441a17d25c3249556f7bf281b1be.squirrel@www.codeaurora.org> <6669559e86c1d13b27e941ff2acf89d2.squirrel@www.codeaurora.org> <000001ccfbf7$ac3e7510$04bb5f30$%jun@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:52015 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518Ab2CKVgy (ORCPT ); Sun, 11 Mar 2012 17:36:54 -0400 In-Reply-To: <000001ccfbf7$ac3e7510$04bb5f30$%jun@samsung.com> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Seungwon Jeon Cc: merez@codeaurora.org, 'Namjae Jeon' , linux-mmc@vger.kernel.org, 'Chris Ball' , linux-kernel@vger.kernel.org > Maya Erez wrote: >> > Hi. Merez. >> > >> > Thanks a lot about your performance measurement. >> > >> > I think that your measurement is enough and correct and the firmwa= re >> > 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 >> > >> > 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 handlin= g) 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 =93dead= =94 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 y= ou 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