[lkml]   [2007]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: O_DIRECT question
    On Sun, Jan 28, 2007 at 06:03:08PM +0100, Denis Vlasenko wrote:
    > I still don't see much difference between O_SYNC and O_DIRECT write
    > semantic.

    O_DIRECT is about avoiding the copy_user between cache and userland,
    when working with devices that runs faster than ram (think >=100M/sec,
    quite standard hardware unless you've only a desktop or you cannot
    afford raid).

    O_SYNC is about working around buggy or underperforming VM growing the
    dirty levels beyond optimal levels, or to open logfiles that you want
    to save to disk ASAP (most other journaling usages are better done
    with fsync instead). Or you can mount the fs in sync mode when you
    deal with users not capable of unmounting devices before unplugging
    them. Ideally you should never need O_SYNC, when you need O_SYNC it's
    usually a very bad sign. If you need O_DIRECT it's not a bad sign
    (needing O_DIRECT is mostly a sign you've a very fast storage).

    The only case where I ever used O_SYNC myself is during backups (when
    run on standard or mainline kernels that dirty half ram during
    backup). For the logfiles I don't find it very useful, if something I
    log them remotely (when system crashes usually the logs won't hit the
    disk anyway, so it's just slower).

    I use "tar | dd oflag=sync" and that generates a huge speedup to the
    rest of the system (not necessairly to the backup itself). Yes I could
    use even oflag=direct, but I'm fine to pass through the cache (the
    backup device runs at 10M/sec through USB, so the copy_user is _sure_
    worth it, if something it will help, it will never be a measurable
    slowdown), what is not fine is to see half of the ram dirty the whole
    time... (hence the need of o_sync).

    O_SYNC and O_DIRECT are useful for different scenarios.
    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: 2007-01-29 18:01    [W:0.019 / U:7.960 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site