linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bharath Ramesh <bramesh-PjAqaU27lzQ@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Question on mlx4 log_num_mtt and log_mtt_per_seg setting
Date: Sun, 20 Jan 2013 22:08:55 -0500	[thread overview]
Message-ID: <50FCB147.7090303@vt.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

I am trying to find the correct setting for log_num_mtt and 
log_mtt_per_seg should be for our cluster. Each node has 64G of RAM. We 
are having issues when running MPI applications, the error is related to 
registering memory. The current setting log_num_mtt=24 and 
log_mtt_per_seg=1. There are lot of conflicting documentations available 
with regards how these settings should be changed. I was wondering if 
the community could explain how these settings works so that we can come 
up with the correct settings that will work in our environment. This 
document [1] specifically says that log_mtt_per_seg should always be 1. 
However, OpenMPI mailing list post [2] talks about different value. Any 
help on this is appreciated. I am not subscribed to the list so would 
really appreciate if I am copied in the replies.

[1] http://www.open-mpi.org/faq/?category=openfabrics#ib-low-reg-mem
[2] http://www.open-mpi.org/community/lists/users/2011/09/17222.php

-- 
Bharath



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3738 bytes --]

             reply	other threads:[~2013-01-21  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  3:08 Bharath Ramesh [this message]
     [not found] ` <50FCB147.7090303-PjAqaU27lzQ@public.gmane.org>
2013-01-21 16:57   ` Question on mlx4 log_num_mtt and log_mtt_per_seg setting Eli Cohen
     [not found]     ` <CAL3tnx4XSQ+iozQpH8btYoDVoYy+715mOJ9zundvdek0e4o6Qw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-21 18:13       ` Bharath Ramesh

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=50FCB147.7090303@vt.edu \
    --to=bramesh-pjaqau27lzq@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;
as well as URLs for NNTP newsgroup(s).