lkml.org 
[lkml]   [2002]   [Feb]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] 2.4.x write barriers (updated for ext3)
Chris Mason [mason@suse.com] wrote:
>
> ..snip..
> >
> > Clearly, there would also have to be a mechanism to flush the cache on
> > unmount, so if this were done by ioctl, would you prefer that the filesystem
> > be in charge of flushing the cache on barrier writes, or would you like the sd
> > device to do it transparently?
>
> How about triggered by closing the block device. That would also cover
> people like oracle that do stuff to the raw device.
>
> -chris

Doing something in sd_release should be covered in the raw case.
raw_release->blkdev_put->bdev->bd_op->release "sd_release".

At least from what I understand of the raw release call path :-).
-Mike
--
Michael Anderson
andmike@us.ibm.com

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

\
 
 \ /
  Last update: 2005-03-22 13:20    [W:0.204 / U:1.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site