lkml.org 
[lkml]   [1998]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Concurrent read/writes on the same file
    Hi,

    On Sun, 13 Dec 1998 17:21:55 +0000, Jamie Lokier
    <lkd@tantalophile.demon.co.uk> said:

    > I meant a read-write semaphore, which it appears we don't have.
    > Why not?

    Because nobody has implemented one yet.

    FWIW, we don't need to lock stuff for write. What we _do_ need is to
    lock allocations, and we need that for both read AND write. I think we
    can probably fix all of the dangerous cases by adding a r/w truncate
    semaphore to the inode, taking it in read mode for reads and writes and
    in write mode for truncate(). That way we maintain concurrency while
    still eliminating the nasty truncate races which caused that semaphore
    to be put there in the first place.

    --Stephen

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:46    [W:0.022 / U:121.304 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site