I'm looking at updating IP-over-InfiniBand to use NAPI, and due to the
way IB works, the driver is going to be susceptible to the rotting
packet problem.  It seems I'm going to have to call netif_rx_reschedule().

However I'm confused about a couple of things, and there are only two
uses of netif_rx_reschedule() in the kernel, so I'm a little stuck.

1. What is the intent of the second, 'undo' parameter?  For example,
   ibmveth.c does

        if(ibmveth_rxq_pending_buffer(adapter) && netif_rx_reschedule(netdev, 
frames_processed))
        {
                lpar_rc = h_vio_signal(adapter->vdev->unit_address, 
VIO_IRQ_DISABLE);
                ibmveth_assert(lpar_rc == H_SUCCESS);
                more_work = 1;
                goto restart_poll;
        }

   but it only does

        netdev->quota -= frames_processed;

   _after_ that block (and the jump back to restart_poll).  So the
   whole things seems fishy: netdev->quota goes up by the number of
   frames processed??

2. What is the return value supposed to be used for?  ibmveth.c
   returns from the poll method if netif_rx_reschedule() returns 0 (ie
   the poll was already scheduled); ibm_emac_mal.c jumps back to
   repoll regardless of the return value, and NAPI_HOWTO.txt has

        if (ring_has_new_packet() && netif_rx_reschedule(dev, received)) {
                disable_rx_and_rxnobufs()
                goto restart_poll
        } while (rx_status_is_set);

   which is not particularly enlightening to say the least...
   if (...) {...} while (...) ?!

   It's not clear to me why the driver would want to do something
   different depending on whether the NAPI poll was already scheduled
   or not.

Thanks,
  Roland
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to