summaryrefslogtreecommitdiffhomepage
path: root/runsc/tools/dockercfg
diff options
context:
space:
mode:
authorAndrei Vagin <avagin@google.com>2018-11-08 17:38:50 -0800
committerShentubot <shentubot@google.com>2018-11-08 17:39:51 -0800
commit2ef122da35899591737adca296b499246b877532 (patch)
tree40750691cc2655f5292a787fecc95435414df353 /runsc/tools/dockercfg
parent5a0be6fa203273d1e4ab06a206eaffeca5724533 (diff)
Implement sync_file_range()
sync_file_range - sync a file segment with disk In Linux, sync_file_range() accepts three flags: SYNC_FILE_RANGE_WAIT_BEFORE Wait upon write-out of all pages in the specified range that have already been submitted to the device driver for write-out before performing any write. SYNC_FILE_RANGE_WRITE Initiate write-out of all dirty pages in the specified range which are not presently submitted write-out. Note that even this may block if you attempt to write more than request queue size. SYNC_FILE_RANGE_WAIT_AFTER Wait upon write-out of all pages in the range after performing any write. In this implementation: SYNC_FILE_RANGE_WAIT_BEFORE without SYNC_FILE_RANGE_WAIT_AFTER isn't supported right now. SYNC_FILE_RANGE_WRITE is skipped. It should initiate write-out of all dirty pages, but it doesn't wait, so it should be safe to do nothing while nobody uses SYNC_FILE_RANGE_WAIT_BEFORE. SYNC_FILE_RANGE_WAIT_AFTER is equal to fdatasync(). In Linux, sync_file_range() doesn't writes out the file's meta-data, but fdatasync() does if a file size is changed. PiperOrigin-RevId: 220730840 Change-Id: Iae5dfb23c2c916967d67cf1a1ad32f25eb3f6286
Diffstat (limited to 'runsc/tools/dockercfg')
0 files changed, 0 insertions, 0 deletions