LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alex Richman <alex.r@gblabs.co.uk>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mlock() confusing 1 half of system RAM limit
Date: Fri, 1 Jun 2018 13:26:59 +0100	[thread overview]
Message-ID: <3e33edd7-89dd-1c09-77df-a2ae23c208f1@gblabs.co.uk> (raw)
In-Reply-To: <20180601114425.GA15686@dhcp22.suse.cz>

I am using a shm MAP_SHARED, along these lines:
 > shm_fd = shm_open(handle, (O_RDWR | O_CREAT), (S_IRWXU | S_IRWXG | 
S_IRWXO));
 > ftruncate(shm_fd, channel->sled_size)
 > channel->sled = mmap(NULL, channel->sled_size, (PROT_READ | 
PROT_WRITE), (MAP_SHARED | MAP_NORESERVE), shm_fd, 0);
 > mlock(channel->sled, channel->sled_size) /* Fails with ENOMEM. */

But shmmax is unlimited on my box:
# sysctl -a | grep shm
kernel.shm_next_id = -1
kernel.shm_rmid_forced = 0
kernel.shmall = 18446744073692774399
kernel.shmmax = 18446744073692774399
kernel.shmmni = 4096

Any ideas?

Many thanks,
- Alex.


On 01/06/18 12:44, Michal Hocko wrote:
> 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.

-- 
Alex Richman
alex.r@gblabs.co.uk
Engineering
GB Labs
2 Orpheus House,
Calleva park,
Reading
RG7 8TA
Tel:+44 (0)118 455 5000
www.gblabs.com



The information contained in this message and any attachment may be proprietary, confidential and privileged.
If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying
of this communication is strictly prohibited. If you received this communication in error, please contact me immediately,
and delete the communication (including attachments, if applicable) from any computer or network system.

  reply	other threads:[~2018-06-01 12:26 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
2018-06-01 12:26   ` Alex Richman [this message]
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:
  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=3e33edd7-89dd-1c09-77df-a2ae23c208f1@gblabs.co.uk \
    --to=alex.r@gblabs.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --subject='Re: mlock() confusing 1 half of system RAM limit' \
    /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

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