linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Rui Machado <ruimario-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mlx4 kernel parameters
Date: Wed, 3 Feb 2010 14:42:00 +0200	[thread overview]
Message-ID: <20100203124200.GA30979@mtls03> (raw)
In-Reply-To: <6978b4af1002030202h431384c4ub6de0313e51c4500-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, Feb 03, 2010 at 11:02:07AM +0100, Rui Machado wrote:
> 
> on trying to change the mlx4_core parameters log_num_mtt and
> log_num_mpt to 21 and 18 respectively, I see the following message:

The MPTs and MTTs are managed by bitmap allocators within the mlx4
core drivers. These allocators requires physically contigous memory
whose size is proportional to the number of controlled resources.
Since Linux does has a limitation on the order of allocated contigous
memory, the allocator might fail to initialize.
> 
> mlx4_core 0000:07:00.0: Failed to initialize memory region table, aborting.
> 
> The objective is to be able to memory-pin large portion of a machine
> with lots of RAM, otherwise we are limited to about 16GB.
> Does anyone has an hint or thoughts on what might be the problem?

For this you can use the parameter log_mtts_per_seg which allows to
define the granulairty of MTTs allocated. So for a given number of MTT
segements (which is what the allocator really allocates), you control
more registered memeory.
As for the number of MPTs, please don't use too large numbers - you
usually don't have to increase this number. 


--
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-02-03 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 10:02 mlx4 kernel parameters Rui Machado
     [not found] ` <6978b4af1002030202h431384c4ub6de0313e51c4500-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-03 12:42   ` Eli Cohen [this message]
2010-02-03 14:17     ` Rui Machado
     [not found]       ` <6978b4af1002030617v4b55787ei4e66f72de662528a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-03 14:54         ` Eli Cohen

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=20100203124200.GA30979@mtls03 \
    --to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ruimario-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).