[lkml]   [2010]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: O_NONBLOCK is NOOP on block devices
    > If O_NONBLOCK is meaningful whatsoever (see man page docs for
    > semantics) against block devices, one would expect a nonblocking io

    It isn't...

    The manual page says "When possible, the file is opened in non-blocking
    mode" . Your write is probably not blocking - but the memory allocation
    for it is forcing other data to disk to make room. ie it didn't block it
    was just "slow".

    O_NONBLOCK on a regular file does influence how it responds to leases and
    mandatory locks.

    > probably be documented for clarity and it would be straight forward
    > for it to return an error if these contradictory behaviors are
    > simultaneously specified, unintentionally of course.

    and risk breaking existing apps.

    > Thoughts anyone?


     \ /
      Last update: 2010-03-03 12:49    [W:0.018 / U:23.440 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site