From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Meyer,
Donald J"
<donald.j.meyer-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mlx4_core unable to use MSI-x on our nodes
Date: Thu, 22 Jul 2010 13:47:01 -0600 [thread overview]
Message-ID: <20100722194701.GO7920@obsidianresearch.com> (raw)
In-Reply-To: <6203933669E90E4AB42B5BC4EDE38D350CF01EF379-qERRe+bbXDTTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Jul 22, 2010 at 10:56:55AM -0700, Meyer, Donald J wrote:
> In our dmesg log I see "mlx4_core 0000:02:00.0: Only 12 MSI-X
> vectors available, need 25. Not using MSI-X" which if I read it
> correctly says our mlx4_core is unable to use MSI-X which if I also
> understand correctly means the mlx4_core can't use the sharing of
> interrupts among all processors.
> If this is correct, do we want to try to fix this so the mlx4_core
> can use MSI-X and share the interrupts?
Yes, you will get better performance with MSI-X, fixing it is
worthwhile..
> And if we do want to fix this, do you have any suggestions for how
> to fix it?
AFAIK, the only way to fix this is to user a newer kernel (or
different build options?).. Some kernels do not provide very many
interrupt vectors so they get exhausted easily.
Ie the 2.6.28 kernel I have here is using vector numbers 2298 for MSI
vectors.. There are lots of interrupts available :)
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-22 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 0:54 Issue with RDMA_CM on systems with multiple IB HCA's Hari Subramoni
[not found] ` <Pine.GSO.4.40.1007212046022.17-100000-ItQMRKI8FOvVp4Hyp30HIZ9NZdITTVap@public.gmane.org>
2010-07-22 7:15 ` Or Gerlitz
[not found] ` <4C47EFFB.1040808-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-07-22 16:41 ` Jonathan Perkins
[not found] ` <AANLkTinco6znrHkoE9vL1n7KrrZ68zPExPUPQeDHD64i-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-22 17:23 ` Hari Subramoni
[not found] ` <Pine.GSO.4.40.1007221320200.17-300000-ItQMRKI8FOvVp4Hyp30HIZ9NZdITTVap@public.gmane.org>
2010-07-22 17:56 ` mlx4_core unable to use MSI-x on our nodes Meyer, Donald J
[not found] ` <6203933669E90E4AB42B5BC4EDE38D350CF01EF379-qERRe+bbXDTTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-07-22 19:47 ` Jason Gunthorpe [this message]
2010-07-25 7:02 ` Yevgeny Petrilin
2010-07-23 20:03 ` Issue with RDMA_CM on systems with multiple IB HCA's Or Gerlitz
[not found] ` <AANLkTi=s4TWfji7Jkz7SipK6WABKGdB5CurhSqPMxXPw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-26 18:42 ` Hari Subramoni
[not found] ` <Pine.GSO.4.40.1007261442050.20664-100000-3mrvs1K0uXjA85jc68Yv76kAi/sjxfazN7jzCyCsa88@public.gmane.org>
2010-07-30 0:20 ` Hari Subramoni
2010-07-23 9:32 ` Larry
[not found] ` <AANLkTinPRAPDZi8xn5zOr5k26-=040N45vVWk1usf8H5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-23 15:48 ` Hefty, Sean
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=20100722194701.GO7920@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=donald.j.meyer-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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