All of lore.kernel.org
 help / color / mirror / Atom feed
From: Håvard Bjerke <havarbj@idi.ntnu.no>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: runejoha@idi.ntnu.no, xen-devel@lists.sourceforge.net
Subject: Re: Report on Virtualization in Clusters
Date: Fri, 26 Nov 2004 14:32:25 +0100	[thread overview]
Message-ID: <20041126133225.GR18329@idi.ntnu.no> (raw)
In-Reply-To: <41A708F3.3020803@diku.dk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1681 bytes --]

On Fri, Nov 26, 2004 at 11:44:03AM +0100, Jacob Gorm Hansen wrote:
> Håvard Bjerke wrote:
> >Rune and I just finished writing a report on using virtualization with Xen 
> >in clusters, with focus on network performance. You may download it from 
> >http://www.idi.ntnu.no/~havarbj/clust_virt.pdf
> >
> >We hope you find it interesting!
> 
> Yes, very interesting. Good work.
> 
> It seems from your tests without interrupt coalescing that Xen has a 
> higher interrupt-handling overhead than native Linux.  I suppose that 
> with the new IO model, Xen needs to flush the TLBs for every interrupt 
> that arrives. Do you think this is the reason for the overhead, or are 
> the performance problems only due to your hardware being badly supported 
> by Xen?

My guess is that it is the former, because we "solved" the problem with the IOAPIC bug with 'ignorebiostables'. Thus using legacy PIC, everything seemed to behave normally except when not using IC.

I think it boils down to whether or not using legacy PIC as opposed to (a supported) IOAPIC has an impact on interrupt handling. If it does, I think it's the latter reason, otherwise I think it's the former.

It would be quite easy to verify on the other cluster. I just couldn't find out how to disable IC on the tg3 driver.

The Xen developers could probably give a better answer, though.

Håvard


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-26 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 12:54 Report on Virtualization in Clusters Håvard Bjerke
2004-11-26 10:44 ` Jacob Gorm Hansen
2004-11-26 13:32   ` Håvard Bjerke [this message]
2004-11-28 11:17     ` Ian Pratt
2004-11-28 11:54       ` Håvard Bjerke
2004-11-26 15:27   ` Rune Johan Andresen
2004-11-26 16:08     ` Håvard Bjerke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041126133225.GR18329@idi.ntnu.no \
    --to=havarbj@idi.ntnu.no \
    --cc=jacobg@diku.dk \
    --cc=runejoha@idi.ntnu.no \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.