From: Håvard Bjerke <Havard.Bjerke@idi.ntnu.no>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: =?unknown-8bit?Q?H=E5vard?= Bjerke <Havard.Bjerke@idi.ntnu.no>,
"Rune Johan Andresen" <Rune.Johan.Andresen@idi.ntnu.no>,
"Xen Virtual Machine Monitor" <xen-devel@lists.sourceforge.net>
Subject: Re: Xen & I/O in clusters - Single Vs. Dual CPU issue
Date: Tue, 2 Nov 2004 17:13:08 +0100 [thread overview]
Message-ID: <20041102161308.GD18329@idi.ntnu.no> (raw)
In-Reply-To: <E1CNchz-0008SC-00@mta1.cl.cam.ac.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1097 bytes --]
On Fri, Oct 29, 2004 at 08:46:46PM +0100, Ian Pratt wrote:
> > The native systems can have either XT-PIC or IOAPIC, and it seems that both have equal performance. In Xen0, however, by looking through dmesg, there doesn't seem to be any IOAPIC. Is it possible to enable (or disable) IOAPIC in Xen0?
>
> If you boot with 'ignorebiostables' on the Xen command line Xen
> will ignore the IOAPIC and use the PIC.
>
> I could believe there might be a lurking performance problem with
> PIC support as it probably hasn't had the same level of
> performance testing as IOAPIC.
>
'ignorebiostables' did the trick. Thanks for the help :)
Now I'm curious about live migration. Is it possible to live migrate an MPI application running on a set of nodes to another set of nodes? Has anyone tried that?
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_id\x12065&op=click
next prev parent reply other threads:[~2004-11-02 16:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:12 plan 9 status Ronald G. Minnich
2004-10-13 12:14 ` Mark A. Williamson
2004-10-13 22:18 ` Ronald G. Minnich
2004-10-14 0:52 ` Kip Macy
2004-10-14 8:10 ` Keir Fraser
2004-10-14 10:35 ` Wesley Parish
2004-10-14 11:04 ` Keir Fraser
2004-10-14 15:32 ` Ronald G. Minnich
2004-10-14 15:57 ` Keir Fraser
2004-10-21 16:06 ` Keir Fraser
2004-10-14 15:53 ` Mark A. Williamson
2004-10-14 17:45 ` Xen & I/O in clusters - problems! Rune Johan Andresen
2004-10-14 18:17 ` Ian Pratt
2004-10-14 23:24 ` Mark A. Williamson
2004-10-15 13:48 ` Rune Johan Andresen
2004-10-21 19:12 ` Xen & I/O in clusters - problems! New Information Rune Johan Andresen
2004-10-21 20:24 ` Ian Pratt
2004-10-22 16:36 ` Rune Johan Andresen
2004-10-22 17:47 ` Ian Pratt
2004-10-27 17:11 ` Håvard Bjerke
2004-10-27 18:26 ` Ian Pratt
2004-10-27 18:40 ` Mark A. Williamson
2004-10-28 11:51 ` Håvard Bjerke
2004-10-28 13:09 ` Mark A. Williamson
2004-10-28 11:32 ` Håvard Bjerke
2004-10-28 12:44 ` Ian Pratt
2004-10-28 16:45 ` Håvard Bjerke
2004-10-29 17:05 ` Xen & I/O in clusters - Single Vs. Dual CPU issue Rune Johan Andresen
2004-10-29 17:24 ` Ian Pratt
2004-10-29 18:39 ` Håvard Bjerke
2004-10-29 19:46 ` Ian Pratt
2004-11-02 16:13 ` Håvard Bjerke [this message]
2004-11-02 16:35 ` Mark A. Williamson
2004-11-02 16:51 ` Mark A. Williamson
2004-11-04 17:42 ` Rune Johan Andresen
2004-11-04 18:41 ` Bin Ren
2004-11-05 14:53 ` Rune Johan Andresen
2004-11-05 16:47 ` Keir Fraser
2004-11-05 17:33 ` Rune Johan Andresen
2004-11-06 8:04 ` Keir Fraser
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=20041102161308.GD18329@idi.ntnu.no \
--to=havard.bjerke@idi.ntnu.no \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Rune.Johan.Andresen@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.