lkml.org 
[lkml]   [2000]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee
       Date: 	Wed, 13 Sep 2000 12:54:49 +0200 (CEST)
    From: Trond Myklebust <trond.myklebust@fys.uio.no>

    Don't forget that 2^20 > 10^6, hence if you really want units of
    microseconds, you actually only need to save 3 bytes worth of data per
    timestamp.

    For the purposes of NFS, however the 'microseconds' field doesn't
    actually have to mean anything. It's just used as a cookie.
    Furthermore, only the mtime field, and to a limited extent the ctime
    field, are used for attribute consistency checking.

    So this is a really stupid question, but I'll ask it anyway. If you
    just need a cookie, is there any way that you might be able to steal a
    few bits from i_generation field for that purpose? (This assumes that
    we only worry about solving the problem for NFS.)

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

    \
     
     \ /
      Last update: 2005-03-22 12:38    [W:3.197 / U:0.368 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site