xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Kristoffer Harthing Egefelt <k@itoc.dk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen
Date: Wed, 28 Mar 2012 14:27:40 +0100	[thread overview]
Message-ID: <4F7311CC.1050709@citrix.com> (raw)
In-Reply-To: <1332926993826-5599935.post@n5.nabble.com>

On 28/03/12 10:29, Kristoffer Harthing Egefelt wrote:
>> How about pci=nomsi on kernel (i.e. vmlinuz) command line?
> That worked! The card is now working with legacy interrupts:
>
> [  143.767091] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25
> [  143.767222] xen: registering gsi 38 triggering 0 polarity 1
> [  143.767238] xen_map_pirq_gsi: returning irq 38 for gsi 38
> [  143.767242] xen: --> pirq=38 -> irq=38 (gsi=38)
> [  143.767245] Already setup the GSI :38
> [  143.767250] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ
> 38
> [  143.767267] qlcnic 0000:03:00.0: setting latency timer to 64
> [  143.768057] qlcnic 0000:03:00.0: 2MB memory map
> [  144.403025] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0,
> [  144.403027] 	max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0,
> [  144.403029] 	max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae
> [  144.411026] qlcnic 0000:03:00.0: failed card response code:0x10
> [  144.411099] qlcnic 0000:03:00.0: Can't get template size 16
> [  144.411102] qlcnic 0000:03:00.0: firmware v4.7.83
> [  144.419028] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port
> Mezzanine Card Board Chip rev 0x54
> [  144.419075] qlcnic 0000:03:00.0: using legacy interrupts
> [  144.419842] qlcnic 0000:03:00.0: eth0: XGbE port initialized
>
> Irq 38 is now visible in /proc/interrupts
>
> But what might the consequences be of this? 
> The NIC currently share irq with the raid card - should I expect a
> performance hit?
> The dom0 is going to have 1 core dedicated.

Out of interest, which version of Xen are you using? (if you have
already said, I apologize - i cant find it from a quick scan of this thread)

There is most certainly a performance hit.  From my bugfixing of
hardware interrupts in the past, line level interrupts take ~30ms to be
services, ranging between extremes of 10ms to 150ms.  XenServer sees an
order of magnitude hard drive performance increase by simply switching
from legacy line interrupts to MSI interrupts for the host disks.

There is no good reason why legacy line interrupts would work while MSIs
don't, which means you have probably found a bug (and indeed, there is a
reason why line level interrupts are legacy and Message Signaled
Interrupts were introduced into the PCI spec in 1995).

~Andrew

> --
> View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599935.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-03-28 13:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  8:48 no-carrier on qlogic 8242 10gig with linux 3.x running xen Kristoffer Harthing Egefelt
2012-03-27  9:25 ` Wei Liu
2012-03-27  9:43   ` Kristoffer Harthing Egefelt
2012-03-27 10:02     ` Wei Liu
2012-03-27 12:41       ` Pasi Kärkkäinen
2012-03-27 16:23         ` Kristoffer Harthing Egefelt
2012-03-27 16:37           ` Wei Liu
2012-03-27 18:45             ` Kristoffer Harthing Egefelt
2012-03-27 18:58               ` Konrad Rzeszutek Wilk
2012-03-27 18:59                 ` Konrad Rzeszutek Wilk
2012-03-27 19:26           ` Pasi Kärkkäinen
2012-03-27 20:29             ` Kristoffer Harthing Egefelt
2012-03-27 21:31               ` Kristoffer Harthing Egefelt
2012-03-27 21:51                 ` Konrad Rzeszutek Wilk
2012-03-27 22:35                   ` Kristoffer Harthing Egefelt
2012-03-28 14:37                     ` Konrad Rzeszutek Wilk
2012-03-29  8:30                       ` Kristoffer Harthing Egefelt
2012-03-29 14:59                         ` Konrad Rzeszutek Wilk
2012-03-29 18:43                           ` Kristoffer Harthing Egefelt
2012-05-10 15:42                             ` Konrad Rzeszutek Wilk
2012-05-13 20:24                               ` Kristoffer Harthing Egefelt
2012-05-23  9:40                                 ` Kristoffer Harthing Egefelt
2012-05-23 14:27                                   ` Pasi Kärkkäinen
2012-05-25 21:03                                   ` Konrad Rzeszutek Wilk
2012-03-28  8:55                 ` Fajar A. Nugraha
2012-03-28  9:29                   ` Kristoffer Harthing Egefelt
2012-03-28 13:27                     ` Andrew Cooper [this message]
2012-03-29  8:35                       ` Kristoffer Harthing Egefelt
2012-03-29 11:50                         ` Andrew Cooper
2012-03-28  9:15               ` Ian Campbell
2012-03-28  9:55                 ` Kristoffer Harthing Egefelt
2012-03-28 10:23                   ` Andrew Cooper
2012-03-28 12:57                     ` Kristoffer Harthing Egefelt
2012-03-28 13:06                       ` Jan Beulich
2012-07-31 21:50       ` Anirban Chakraborty

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=4F7311CC.1050709@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=k@itoc.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).