lkml.org 
[lkml]   [2003]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)
    David S. Miller wrote:
    > This is very different from how you are using the lock+rtnl scheme
    > for your ATM stuff.

    What should help in the ATM code is that it pushes synchronization
    "down", i.e. "close" functions usually can't return until they are
    truly done (or at least have made sure there is nothing externally
    visible left).

    In the case of devices, delayed removal is possible, but is then
    initiated when closing a VCC (VCCs act as an implicit reference
    count for devices), which is another synchronous operation.

    VCC creation/removal in response to other asynchronous activity,
    e.g. after ARP, is relayed through user-space demons, which then
    make normal system calls to implement the change.

    - Werner

    --
    _________________________________________________________________________
    / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
    /_http://www.almesberger.net/____________________________________________/
    -
    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-03-22 13:36    [W:0.021 / U:89.404 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site