lkml.org 
[lkml]   [2010]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Deadlock in NFSv4 in all kernels
    On Tue, May 25, 2010 at 09:45:32AM -0400, William A. (Andy) Adamson wrote:
    > Not get into the problem in the first place: this means
    >
    > 1) determine a 'lead time' where the NFS client declares a context
    > expired even though it really as 'lead time' until it actually
    > expires.
    >
    > 2) flush all writes on any contex that will expire within the lead
    > time which needs to be long enough for flushes to take place.

    I think you cannot give any guarantees that the flush happens on time. There
    can be server overload, network overload, anything and you are out of luck.

    --
    Lukáš Hejtmánek
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2010-05-25 16:05    [W:0.035 / U:0.644 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site