Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754068Ab2FNHqd (ORCPT ); Thu, 14 Jun 2012 03:46:33 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:53770 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752831Ab2FNHqa (ORCPT ); Thu, 14 Jun 2012 03:46:30 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6741"; a="198554037" Message-ID: <3ec17ded5b5a72a1d45d97a4d820cd48.squirrel@www.codeaurora.org> In-Reply-To: References: <1338576911-17089-1-git-send-email-merez@codeaurora.org> <1338576911-17089-2-git-send-email-merez@codeaurora.org>

Date: Thu, 14 Jun 2012 00:46:30 -0700 (PDT) Subject: Re: [PATCH v2 1/1] mmc: block: Add write packing control From: merez@codeaurora.org To: "Muthu Kumar" Cc: merez@codeaurora.org, linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org, "DOCUMENTATION" , "open list" User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2581 Lines: 77 On Wed, June 13, 2012 3:21 pm, Muthu Kumar wrote: > On Wed, Jun 13, 2012 at 12:52 PM, wrote: >> >> On Mon, June 11, 2012 5:28 pm, Muthu Kumar wrote: >>> On Mon, Jun 11, 2012 at 2:19 PM, Muthu Kumar >>> wrote: >>>> On Fri, Jun 1, 2012 at 11:55 AM, Maya Erez >>>> wrote: >>>>> trigger >>>>> the packing can be configured via sysfs by writing the required value >>>>> to: >>>>> /sys/block//num_wr_reqs_to_start_packing. >>>>> The trigger for disabling the write packing is fetching a read >>>>> request. >>>>> >>>> >>>> If it is applicable only to MMC why do we have this sysfs attr for all >>>> block devices? >>> >>> Just to be clear, please create a directory, say mmc, under >>> /sys/block// and create the attr inside that. >>> >>> You can refer to dm (dm-sysfs.c) for sample implementation. >> I understand why you think it would be best to distinguish the MMC >> specific attribute from the general block devices attributes. >> However, since this attribute is created only for the MMC block device, >> other block devices won't be aware of it. > > I understand its created by the MMC code so will not be there for > other block devices. But having the device specific attributes inside > one directory is better/cleaner. And since we are already > following that model for other devices, why not follow that for MMC > also? > >> Therefore, it doesn't >> necessarily require a separation to a different folder. >> Currently there is another MMC specific attribute (force_ro) which is >> also >> created in the root directory. I think it would be better to also create >> the num_wr_reqs_to_start_packing in the same folder as force_ro and not >> make it an exceptional attribute in its location and the code that >> handles >> it. > > Then time to move that as well to "mmc" directory. > > Regards, > Muthu I will make this change for the new attribute and for force_ro as well. Thanks, Maya > > >> I would appreciate your opinion on that. >> >> Thanks, >> Maya >> -- >> Sent by consultant of Qualcomm Innovation Center, Inc. >> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum >> > -- Sent by consultant of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/