Hi Sean, On Wed, 3 Jun 2026 at 11:43, Sean Anderson <[email protected]> wrote: > > On 5/28/26 23:44, [email protected] wrote: > > From: Denis Mukhin <[email protected]> > > > > Introduce `flush` subcommand for all blk devices to allow committing > > dirty data explicitly to the given block device. > > Shouldn't this be done automatically as part of blk_write? Similar to > how all FS operations in U-Boot look like > > - Mount FS > - Perform operation > - Unmount FS > > so the FS is never in an inconsistent state once an operation completes. > > Is the performance impact too much? I'm just concerned that a lot of > existing code assumes that blk_write is persistent and that it's OK > to e.g. immediately reset after blk_write returns.
This is actually for a device-level flush, so more like a Linux 'sync' than just a write. If the hardware supports / requires it, then it seems valuable to me. Regards, Simon
