On Tuesday 12 June 2012, Saugata Das wrote: > > I don't think that is correct. The most obvious implementation in eMMC > > hardware for this would be to group all data from one context to be > > written into the same erase block, in order to reduce the amount > > of garbage collection that needs to happen at erase time. AFAICT, > > the main interest here is, as Ted is guessing correctly, to make sure > > that all data which gets written into one context has roughly the > > same life time before it gets erased or overwritten. > > The restriction is there on "large unit" context, which prevents > trim/erase of the blocks till the context is active. But we do not > enable "large unit". On non-"large unit" context, the specification > does not restrict the trim/erase of blocks based on context. As I said, it's not a technical limitation, but a logical conclusion from trying to use the context ID for something useful. The only reason to use context ID in the first place is to reduce the amount of garbage collection in the device (improving performance and expected life of the device), so any context ID annotations we make should be directed at giving useful information to the device to actually do that. Arnd -- 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
