> Our intent was to get an idea of user-initiated sync block I/O because
> there is some expectation from user space that a higher I/O priority will
> result in lower delays for such I/O. General throttling writes wouldn't
> fit in
> this category though msync and O_SYNC would.
>
> Are there a lot of other paths you see ? I'll root around more but if you
> could just list a few more, it'll help.
unmount
-o sync mounts
last-close kind of syncs on block devices (yes databases do this and
care)
fdatasync()/fsync()
open() (does a read seek, and may even do cluster locking stuff)
flock()
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
