This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] confusion on front end driver and allox_rx_buffers.

To: "Ronald G. Minnich" <rminnich@xxxxxxxx>
Subject: Re: [Xen-devel] confusion on front end driver and allox_rx_buffers.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 15 Sep 2004 10:48:38 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Sep 2004 10:55:54 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 14 Sep 2004 22:09:58 MDT." <Pine.LNX.4.58.0409142155100.2212@xxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> OK, the question: I only consumed one buffer, why is this code refilling 
> the whole ring this way? What's happening to me is that the id = 
> GET_ID_FROM_FREELIST is failing badly because the do loop is running from 
> 2 to NETIF_RX_RING_SIZE, which is wrong. 

The key insight is that you won't necessarily be getting an interrupt
callback for every packet received. e.g., under high load multiple
interrupts end up getting collapsed together into one callback.

Also, you'll notice that at the top of the refill function we don't
enter the refill loop unless there is a decent batch of work to be
done -- this amortizes the cost of the MEMOP_decrease_reservation

 -- Keir

> I think I'm getting caught between the differences in Plan 9 and Linux net 
> interrupt handling, which I don't fully understand yet, but some of this 
> ether xen front end code has me confused. 
> Comments and clarification are most welcome :-)

This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>