Hi Tejun
Thank you for the detailed explanation!
Best Regards
Tanya Brokhman
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a
member of Code Aurora Forum, hosted by The Linux Foundation
On 4/9/2013 10:03 PM, Tejun Heo wrote:
Hey,
On Mon, Apr 08, 2013 at 07:19:19AM +030
Hey,
On Mon, Apr 08, 2013 at 07:19:19AM +0300, Tanya Brokhman wrote:
> completed after the FLUSH. But perhaps there is a correct way to
> move the implementation of "ordering around the flush" to the block
> layer? Not that it would work better, it just feels that logically -
> block layer is the
Hi Tejun,
Thank you for the prompt response.
Which version of kernel are you looking at? The barrier / flush
implementation went through several iterations and in the current
iteration ordering of requests around the flush request is the
responsibility of higher layer - ie. filesystems are req
Hey,
On Sun, Apr 07, 2013 at 04:15:30PM +0300, Tanya Brokhman wrote:
> I've been looking into the flush implementation, trying to
> understand how it works. FLUSH command can be used for two purposes:
> 1. Flush the data to the non-volatile memory from the card cache
> 2. Keep an order of requests
Hello Tejun,
I'm writing to you since you're signed on the blk-flush.c file, hoping
you could answer a flush-related question for me. Please excuse me if
you're not the right person to address this to.
I've been looking into the flush implementation, trying to understand
how it works. FLUSH
