Lines Matching refs:we

36 load the more we could clean up the rxring
38 the load the more times we couldnt clean up the rxring.
102 we are enabling interrupts. We only get to know about such a packet when the 
105 which for clarity we'll refer to as the "rotting packet".
133 For the rest of this text, we'll assume that dev->poll() only
168 Below we describe what kind of changes are required for NAPI to work.
304 				/* tell system we have work to be done. */
339 interrupt sources we wish to avoid. The two common ones are a) a packet 
347 gets successfully added to the core poll list. If we get a zero value
348 we can _almost_ assume are already added to the list (instead of not running. 
468                 if (--rx_work_limit < 0) { /* we got packets, but no quota */
505 	/* no packets on ring; but new ones can arrive since we last 
515 	they'll be caught by the while check and we go back and clear them 
516 	since we havent exceeded our quota */
525         /* If RX ring is not full we are out of memory. */
529 	/* we are happy/done, no more packets on ring; put us back
530 	to where we can start processing interrupts again */
565         return 0;  /* we'll take it from here so tell core "done"*/
571 From above we note that:
576 3) instead of netif_rx() we call netif_receive_skb() to pass the skb.
577 4) we have a new way of handling oom condition
579 ensuring that if a new packet has come in, after we are all set and done,
580 and we have not exceeded our quota that we continue sending packets up.
592         /* If RX ring is not full we are still out of memory.
593 	   Restart the timer again. Else we re-add ourselves 
600 	else netif_rx_schedule(dev);  /* we are back on the poll list */
609 In order to debug some of the new features, we introduce new stats
617 if the system is slow in grabbing them and we have a high input
620 Under low load, we might have a single interrupt per packet.
623 Note FC in itself is a good solution but we have found it to not be
646 If we take the example of the tulip:
650 we clear it the first time)
651 Very important is the fact that if we turn on the interrupt bit on when
654 If we cleared the rx ring and proclaimed there was "no more work
655 to be done" and then went on to do a few other things;  then when we enable
667                 /* No packets, but new can arrive while we are doing this*/
683 we are counting that CSR5 will be set in that small window of opportunity
684 and that by re-enabling interrupts, we would actually triger an interrupt
720 might come in, we attempt to re-add ourselves to the poll list.