From: Rui Machado <ruimario-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mlx4 kernel parameters
Date: Wed, 3 Feb 2010 15:17:17 +0100 [thread overview]
Message-ID: <6978b4af1002030617v4b55787ei4e66f72de662528a@mail.gmail.com> (raw)
In-Reply-To: <20100203124200.GA30979@mtls03>
Hi there,
>>
>> 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.
Great, thanks. I increased the log_mtts_per_seg to 5 and was able to
register more memory. But one question remaining: what is then the
maximum memory that one is able to register? 5 is the maximum value to
this parameter, so what does it mean?
cheers,
Rui
--
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-02-03 14:17 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
2010-02-03 14:17 ` Rui Machado [this message]
[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=6978b4af1002030617v4b55787ei4e66f72de662528a@mail.gmail.com \
--to=ruimario-re5jqeeqqe8avxtiumwx3w@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 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).