On 1/13/12, Chris Ball <cjb@xxxxxxxxxx> wrote: > Hi, > > On Thu, Jan 12 2012, S, Venkatraman wrote: >> On Wed, Dec 21, 2011 at 1:09 PM, Saugata Das <saugata.das@xxxxxxxxxxxxxx> >> wrote: >>> From: Saugata Das <saugata.das@xxxxxxxxxx> >>> >>> 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 <saugata.das@xxxxxxxxxx> >> >> I tested this on a device which supports a data tag unit size of 8K. >> Tested-by: Venkatraman S <svenkatr@xxxxxx> > > 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. I'm afraid it that it's really required since some features. data tag, context id, and packed command, are not mutual exclusive. so I hope to make it select. I mean it's not measured the real performance gain and/or other feature. so hope to enable/disable by platform data. How do you think? Thank you, Kyungmin Park > > Thanks, > > - Chris. > -- > Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> > One Laptop Per Child > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
