From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Fraser <keir.xen@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: megasas stops I/O when running kernel as dom0 under xen4.1/4.2
Date: Tue, 30 Aug 2011 13:11:29 +0100 [thread overview]
Message-ID: <4E5CD371.4030609@citrix.com> (raw)
In-Reply-To: <4E5CD13B.6020101@leuphana.de>
On 30/08/11 13:02, Andreas Olsowski wrote:
> --snip--
> > Apologies - previous patch fails to compile (i forgot to hg qrefresh
> > before sending - it has been a very long day). Try this patch.
> Testing right now, so far it seems to do fine, patching worked, so did
> compilation.
>
> A scenario that previously stopped io does no longer stop it.
>
> Ill give it a couple of more tries and days, but it sure looks good.
>
> Any chance of introducing this patch into xen-4.1-testing and making
> it a part of the upcoming xen-4.1.2?
>
>
> with best regards,
>
> Andreas
>
That is up to Keir. My opinion is that this patch is more of a hack
than a solution, especially as it does involve changing the API for
interrupt ops, but that does not necessarily prevent it from being included.
I will soon be working on some significant changes to the interrupt code
(cleanup of structures, cleanup of logic - specifically the logic which
is now false with per-cpu IDTs) with an intension to upstream them, but
whether these patches are suitable to backport is an entirely different
question.
On a completely different note, we have got in contact with LSI who are
altering their driver to consider MSI interrupts as well as MSI-X
interrupts, which will be sensible to take, as MSI interrupts will give
you an order of magnitude faster disk IO, irrespective of the line level
bug in Xen.
~Andrew
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2011-08-30 12:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 13:59 megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Andreas Olsowski
2011-08-11 16:27 ` Simon Rowe
2011-08-11 22:51 ` Konrad Rzeszutek Wilk
2011-08-12 6:31 ` xen.frontend flag for higher display resolution (vnc) for HVM domU domains Mark Schneider
2011-08-12 7:26 ` Marc - A. Dahlhaus
2011-08-12 7:42 ` megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Simon Rowe
2011-08-12 9:11 ` Andreas Olsowski
2011-08-12 9:23 ` Simon Rowe
2011-08-15 10:49 ` Simon Rowe
2011-08-15 12:52 ` Andreas Olsowski
2011-08-19 12:28 ` Andrew Cooper
2011-08-19 14:17 ` Andreas Olsowski
2011-08-19 14:57 ` Andrew Cooper
2011-08-19 16:37 ` Andreas Olsowski
2011-08-19 16:49 ` Andrew Cooper
2011-08-19 18:10 ` Andreas Olsowski
2011-08-22 9:05 ` Andrew Cooper
2011-08-24 12:06 ` Andrew Cooper
2011-08-24 16:57 ` Andrew Cooper
2011-08-24 17:09 ` Konrad Rzeszutek Wilk
2011-08-24 17:20 ` Andrew Cooper
2011-08-26 18:16 ` Andrew Cooper
2011-08-26 18:32 ` Andrew Cooper
2011-08-30 12:02 ` Andreas Olsowski
2011-08-30 12:11 ` Andrew Cooper [this message]
2011-08-30 12:46 ` Keir Fraser
2011-08-12 9:02 ` Simon Rowe
2011-08-12 16:26 ` Pasi Kärkkäinen
2011-08-15 7:44 ` Simon Rowe
2011-08-12 16:25 ` Pasi Kärkkäinen
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=4E5CD371.4030609@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=andreas.olsowski@leuphana.de \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.