WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Interrupt Coalescence

To: "Hevard Bjerke" <havarbj@xxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Interrupt Coalescence
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 12 Nov 2004 08:33:26 -0000
Delivery-date: Fri, 12 Nov 2004 08:58:21 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
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
Thread-index: AcTIjRdyW5FZiVzNSpe2TVHmI0N9aQABH7Vg
Thread-topic: [Xen-devel] Interrupt Coalescence
> I've found that Interrupt Coalescence (IC) has a detrimental 
> effect on some benchmarks with the e1000 driver. So I tried 
> disabling it with the argument "InterruptThrottleRate=0,0".
> 
> This had the wanted effect in native linux, ie. full speed, 
> 116 MB/s. However, in Xen0, disabling IC has the effect of 
> severely reducing bandwidth down to around 1 MB/s.

I'd like to get to the bottom of this. A couple of people have reported odd 
performance anomalies with e1000's, but ours seem to work just fine.

Are you results measured from dom0 or from another domain? If the latter, 
what's the CPU assignment?

What happenes if you boot with 'igrnorebiostables' on the Xen command line 
(this forces uniprocessor)?  This will use the legacy PIC rather than the 
IOAPIC.

The dramatic reduction in bandwidth you're seeing with coallescing on is 
probably our best chance of tracking down this bug (everyone else was seeing 
more subtle effects).

Ian

> Turning of IC has the effect that an interrupt is generated 
> from the NIC for each received or sent MTU (1500 bytes). On a 
> gigabit network this means that an interrupt may be 
> generated, according to 
> [http://www.pam2004.org/papers/265.pdf], every 12 us.
> 
> I looked at #interrupts generated with and without IC, and 
> they are ~ 1100 and ~ 400 respectively when sending a 2 MB 
> message with ttcp.
> 
> So I'm trying to explain what's happening. Is Xen slower in 
> handling the interrupts than native? The CPU is an Intel P4 @ 
> 3400 MHz. Does it need more than 12 us to do a context switch 
> when using Xen?
> 
> 
> Håvard
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE 
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_idU88&alloc_id065&op=ick
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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