[lkml]   [2003]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectdrivers/net/isa-skeleton.c queue management bug?
    I realize that the code is going on ten years old and isn't supposed
    to be run, but is there a bug in the interface queue handling for
    packet transmissions in isa-skeleton.c?

    If TX_RING is defined, net_interrupt() will check to see if it was
    called due to a completed packet, and if so, then it executes:

    if (status & TX_INTR) {
    /* Transmit complete. */

    However, the net_tx() function processes any completed entries and
    then executes:

    if (netif_queue_stopped(dev) && ! tx_full(dev))

    It seems that the queue is going to be awoken in net_interrupt,
    regardless of the state of the ring buffer. I'm not exactly sure
    under what circumstances this might occur, but I'm trying to track
    down random hangs in a driver that is based on isa-skeleton.

    -----|----- W 240-283-1700
    *>=====[]L\ M 505-463-1896
    ' -'-`- KC5RNF
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:34    [W:0.019 / U:13.188 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site