[lkml]   [2006]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch 1/1] sys_sync_file_range()
    On Wednesday March 29, wrote:
    > From: Andrew Morton <>
    > Remove the recently-added LINUX_FADV_ASYNC_WRITE and LINUX_FADV_WRITE_WAIT
    > fadvise() additions, do it in a new sys_sync_file_range() syscall
    > instead.

    Hmmm... any chance this could be split into a sys_sync_file_range and
    a vfs_sync_file_range which takes a 'struct file*' and does less (or
    no) sanity checking, so I can call it from nfsd?

    Currently I implement COMMIT (which has a range) with a by messing
    around with filemap_fdatawrite and filemap_fdatawait (ignoring the
    range) and I'd rather than a vfs helper.

    And in nfsd I call filp->f_op->fsync between the two. Doesn't
    sys_sync_file_range need to call into the filesystem at all?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-03-30 10:04    [W:0.019 / U:23.536 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site