LKML Archive on
help / color / mirror / Atom feed
From: Michal Hocko <>
To: Alex Richman <>
Subject: Re: mlock() confusing 1 half of system RAM limit
Date: Fri, 1 Jun 2018 13:44:25 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri 01-06-18 10:53:57, Alex Richman wrote:
> Hi,
> I'm seeing a 1/2 of system RAM limit when calling mlock().  mlock(2) says:
> > ENOMEM (Linux 2.4 and earlier) the calling process tried to lock more than
> half of RAM.
> Which implies to me that the 1 half of system RAM limit should be only Linux
> 2.4 and earlier, but I'm running linux 4.4.127 and still seeing the limit.
> This is on a system with 66007168 KB total memory, locking 33794621440 bytes
> works, locking 33795653632 bytes does not work.

I assume you are doing mlock on MAP_SHARED resp. on mmap of shmem
file. You are likely to hit the shmem limit. This is half of the
available memory by default.
Michal Hocko

  reply	other threads:[~2018-06-01 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  9:53 Alex Richman
2018-06-01 11:44 ` Michal Hocko [this message]
2018-06-01 12:26   ` Alex Richman
2018-06-01 13:05     ` Michal Hocko
2018-06-01 13:24       ` Alex Richman
2018-06-01 13:41         ` Michal Hocko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: mlock() confusing 1 half of system RAM limit' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).