public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Arthur Kepner <akepner-sJ/iWh9BUns@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH/RFC] mlx4_core: module param to limit msix vec allocation
Date: Sun, 13 Jun 2010 09:53:24 +0300	[thread overview]
Message-ID: <20100613065324.GA2408@eli-vm> (raw)
In-Reply-To: <20100610165921.GF22247-sJ/iWh9BUns@public.gmane.org>

On Thu, Jun 10, 2010 at 09:59:21AM -0700, Arthur Kepner wrote:
> 
> The mlx4_core driver allocates 'nreq' msix vectors (and irqs), 
> where:
> 
>   nreq = min_t(int, dev->caps.num_eqs - dev->caps.reserved_eqs,
>                num_possible_cpus() + 1);
> 
> ConnectX HCAs support 512 event queues (4 reserved). On a system 
> with enough processors, we get:
> 
>   mlx4_core 0006:01:00.0: Requested 508 vectors, but only 256 MSI-X vectors available, trying again
> 
> Further attempts (by other drivers) to allocate interrupts fail, 
> because mlx4_core got 'em all.
> 
> How about this?
> 

Hi Arthur,

how many CPU cores are in your system? What kernel version did you
use?
--
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

  parent reply	other threads:[~2010-06-13  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 16:59 [PATCH/RFC] mlx4_core: module param to limit msix vec allocation Arthur Kepner
     [not found] ` <20100610165921.GF22247-sJ/iWh9BUns@public.gmane.org>
2010-06-13  6:53   ` Eli Cohen [this message]
2010-06-14 15:23     ` Arthur Kepner
2010-06-17 14:53   ` Yevgeny Petrilin
     [not found]     ` <E113D394D7C5DB4F8FF691FA7EE9DB4439A77CCD66-WQlSmcKwN8Te+A/uUDamNg@public.gmane.org>
2010-06-17 21:27       ` Arthur Kepner

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=20100613065324.GA2408@eli-vm \
    --to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=akepner-sJ/iWh9BUns@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