summaryrefslogtreecommitdiffstats
path: root/lib/libusb/libusb20.h
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2013-05-02 20:00:11 +0000
committerkib <kib@FreeBSD.org>2013-05-02 20:00:11 +0000
commit3bbdcb77fd843ff34a0054bea92392cee78dd0ec (patch)
tree3d13940b8e5b2c39fe1b2f1bd66d3d77f1b208eb /lib/libusb/libusb20.h
parent4f1c369b1ff5e5dc0b3c3ac6af693afa2cb40d9a (diff)
downloadFreeBSD-src-3bbdcb77fd843ff34a0054bea92392cee78dd0ec.zip
FreeBSD-src-3bbdcb77fd843ff34a0054bea92392cee78dd0ec.tar.gz
The fsync(2) call should sync the vnode in such way that even after
system crash which happen after successfull fsync() return, the data is accessible. For msdosfs, this means that FAT entries for the file must be written. Since we do not track the FAT blocks containing entries for the current file, just do a sloppy sync of the devvp vnode for the mount, which buffers, among other things, contain FAT blocks. Simultaneously, for deupdat(): - optimize by clearing the modified flags before short-circuiting a return, if the mount is read-only; - only ignore the rest of the function for denode with DE_MODIFIED flag clear when the waitfor argument is false. The directory buffer for the entry might be of delayed write; - microoptimize by comparing the updated directory entry with the current block content; - try to cluster the write, fall back to bawrite() if low on resources. Based on the submission by: bde MFC after: 2 weeks
Diffstat (limited to 'lib/libusb/libusb20.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud