From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Ball Subject: Re: [PATCH] MMC-4.5 Data Tag Support Date: Thu, 12 Jan 2012 14:18:24 -0500 Message-ID: References: <1324453157-30081-1-git-send-email-saugata.das@stericsson.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from void.printf.net ([89.145.121.20]:36721 "EHLO void.printf.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752926Ab2ALTSf (ORCPT ); Thu, 12 Jan 2012 14:18:35 -0500 In-Reply-To: (Venkatraman S.'s message of "Thu, 12 Jan 2012 19:58:29 +0530") Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: "S, Venkatraman" Cc: Saugata Das , linux-mmc@vger.kernel.org Hi, On Thu, Jan 12 2012, S, Venkatraman wrote: > On Wed, Dec 21, 2011 at 1:09 PM, Saugata Das wrote: >> From: Saugata Das >> >> MMC-4.5 data tag feature will be used to store the file system >> meta-data in the >> tagged region of eMMC. This will improve the write and subsequent >> read transfer >> time for the meta data. >> >> Signed-off-by: Saugata Das > > I tested this on a device which supports a data tag unit size of 8K. > Tested-by: Venkatraman S Thanks for testing! I've pushed it to mmc-next. > Chris, > Can this go into 3.3 ? I think 3.4 would be better after a full round of linux-next testing, since this sounds like it could expose card-dependent quirks that could destroy filesystems. Better to be safe. Thanks, - Chris. -- Chris Ball One Laptop Per Child