lkml.org 
[lkml]   [2005]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC][PATCH 0/3] TCP/IP Critical socket communication mechanism
    From
    Date
    > Why not do it the other way? "If you don't hear from me for 2 minutes,
    > do a switchover". Then all you have to do is _not_ to send a packet --
    > easier to do.
    >
    > Anything else seems overkill.
    > Pavel

    Because in some of the scenarios, including ours, it isn't a
    simple failover to a known alternate device or configuration --
    it is reconfiguring dynamically with information received on a
    socket from a remote machine (while the swap device is unavailable).
    Limited socket communication without allocating new memory
    that may not be available is the problem definition. Avoiding the
    problem in the first place (your solution) is effective if you
    can do it, of course. The trick is to solve the problem when you
    can't avoid it. :-)

    +-DLS

    -
    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: 2005-12-21 10:40    [W:0.024 / U:93.544 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site