On Sat, Mar 08, 2014 at 09:59:14PM +0900, Roman Pen wrote:
> From: Roman Peniaev
>
> mtd_blkdevs is device with volatile cache (writeback buffer), so it should
> support
> REQ_FLUSH to do explicit flush.
>
> Without this patch 'sync' does not guarantee that writeback buffer will be
> flushed
>
From: Roman Peniaev
mtd_blkdevs is device with volatile cache (writeback buffer), so it should
support
REQ_FLUSH to do explicit flush.
Without this patch 'sync' does not guarantee that writeback buffer will be
flushed
on disk in case of power off, e.g.:
$ cp some_file /mnt
$ sync
### P
On Fri, Mar 7, 2014 at 3:44 PM, Brian Norris
wrote:
> On Thu, Jan 02, 2014 at 01:21:21AM +0900, Roman Pen wrote:
>> From: Roman Peniaev
>>
>> mtd_blkdevs is device with volatile cache (writeback buffer), so it should
>> support
>> REQ_FLUSH to do explicit flush.
>>
>> Without this patch 'sync' d
On Thu, Jan 02, 2014 at 01:21:21AM +0900, Roman Pen wrote:
> From: Roman Peniaev
>
> mtd_blkdevs is device with volatile cache (writeback buffer), so it should
> support
> REQ_FLUSH to do explicit flush.
>
> Without this patch 'sync' does not guarantee that writeback buffer will be
> flushed
>
From: Roman Peniaev
mtd_blkdevs is device with volatile cache (writeback buffer), so it should
support
REQ_FLUSH to do explicit flush.
Without this patch 'sync' does not guarantee that writeback buffer will be
flushed
on disk in case of power off, e.g.:
$ cp some_file /mnt
$ sync
### P
5 matches
Mail list logo