Re: [RFC PATCH v2] Add new elevator ops for request hint

[Vivek Goyal]

On Thu, Aug 11, 2011 at 09:42:16AM +0900, Kyungmin Park wrote:
> Hi Jens
> 
> Now eMMC device requires the upper layer information to improve the data
> performance and reliability.
> 
> . Context ID
> Using the context information, it can sort out the data internally and improve the performance.
> The main problem is that it's needed to define "What's the context". 
> Actually I expect cfq queue has own unique ID but it doesn't so decide to use the pid instead
> 

Hi,

Can you please give little more details about the optimization you will
do with this pid information?

Also what happens in the case of noop and deadline which don't maintain
per process queues and can't provide this information.

> . Data Tag
> Using the Data Tag (1-bit information), It writes the data at SLC area when it's hot data. So it can make the chip more reliable.

Sorry, I am not very familiar with flash technology. Can you please give
some more details that what do you do with this information about "hot"
data and how does that make chip more reliable.

> First I expect the REQ_META but current ext4 doesn't pass the WRITE_META. only use the READ_META. so it needs to investigate it.

So are you planning to later fix file systems to appropriately mark meta
data requests?

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/