All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bharath Ramesh <bramesh-PjAqaU27lzQ@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Question on mlx4 log_num_mtt and log_mtt_per_seg setting
Date: Mon, 21 Jan 2013 13:13:15 -0500	[thread overview]
Message-ID: <50FD853B.7090705@vt.edu> (raw)
In-Reply-To: <CAL3tnx4XSQ+iozQpH8btYoDVoYy+715mOJ9zundvdek0e4o6Qw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

Hi Eli,
     Thanks a lot for this explanation of the MTT and how 
log_mtt_per_seg log_num_mtt work. I will play around with these values 
and figure which one works best for our cluster + application environment.

--
Bharath

On 1/21/2013 11:57 AM, Eli Cohen wrote:
> Hi Bharath,
>
> each MTT entry is used to cover a whole page. Assuming page size in
> you system equals 4K, the max total of registered memory is 2^(12+24)
> which is 64 GB.
> The log_mtt_per_seg param denotes the granularity of the allocator
> managing MTTs. So, in your case, MTTs are allocated in granularity of
> 2. So if you try to allocate 3 MTTs, you'll end up consuming 4.
> Moreover, the MTT allocator is a buddy allocator that allocates power
> of 2 MTT segments. So if you register memory that requires (2^15 + 1)
> MTTs, you'll actually consume 2^16 MTTs!
>
> In your case I would try to use 2^25 MTTs and log_mtt_per_seg=1. If
> the driver fails to load (probably because the allocator fails to
> allocate memory), try to use 2^24 and 2^2 etc.
>
> I hope that helps.
>
>
>
> On Mon, Jan 21, 2013 at 5:08 AM, Bharath Ramesh <bramesh-PjAqaU27lzQ@public.gmane.org> wrote:
>> 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
>>
>>


-- 
Bharath



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

      parent reply	other threads:[~2013-01-21 18:13 UTC|newest]

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

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=50FD853B.7090705@vt.edu \
    --to=bramesh-pjaqau27lzq@public.gmane.org \
    --cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.