On Tue, Mar 31 2009, Tejun Heo wrote:Hello,
Theodore Tso wrote:On Mon, Mar 30, 2009 at 10:15:51AM -0400, Chris Mason wrote:How about having something like blk_ensure_cache_flushed() whichI'm not sure we want to stick Fernando with changing how barriers areWell, his patch actually added some calls to block_issue_flush(). But
done in individual filesystems, his patch is just changing the existing
call points.
yes, it's probably better if he just changes the existing call points,
and we can have the relevant filesystem maintainers double check to
make sure that there aren't any new call points which are needed.
issues flush iff there hasn't been any write since the last flush?
It'll be easy to implement and will filter out duplicate flushes in
most cases.
My original ide implementation of flushes actually did this. My memory
is a little hazy on why it was dropped, I'm guessing because it
basically never triggered anyway.