问题 Linux:由于虚拟内存限制,无法在单个进程中分配超过32 GB / 64 GB的内存


我有一台128 GB RAM的计算机,运行Linux(3.19.5-200.fc21.x86_64)。但是,我不能在一个进程中分配超过30 GB的RAM。超出此, malloc 失败:

#include <stdlib.h>
#include <iostream>

int main()
{
   size_t gb_in_bytes = size_t(1)<<size_t(30); // 1 GB in bytes (2^30).
   // try to allocate 1 block of 'i' GB.
   for (size_t i = 25; i < 35; ++ i) {
      size_t n = i * gb_in_bytes;
      void *p = ::malloc(n);
      std::cout << "allocation of 1 x " << (n/double(gb_in_bytes)) << " GB of data. Ok? " << ((p==0)? "nope" : "yes") << std::endl;
      ::free(p);
   }
}

这会产生以下输出:

/tmp> c++ mem_alloc.cpp && a.out

allocation of 1 x 25 GB of data. Ok? yes
allocation of 1 x 26 GB of data. Ok? yes
allocation of 1 x 27 GB of data. Ok? yes
allocation of 1 x 28 GB of data. Ok? yes
allocation of 1 x 29 GB of data. Ok? yes
allocation of 1 x 30 GB of data. Ok? yes
allocation of 1 x 31 GB of data. Ok? nope
allocation of 1 x 32 GB of data. Ok? nope
allocation of 1 x 33 GB of data. Ok? nope
allocation of 1 x 34 GB of data. Ok? nope

我搜索了一段时间,发现这与最大虚拟内存大小有关:

~> ulimit -all
[...]
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
virtual memory          (kbytes, -v) 32505856
[...]

我可以将此限制增加到~64 GB ulimit -v 64000000,但不是更进一步。除此之外,我明白了 operation not permitted 错误:

~> ulimit -v 64000000
~> ulimit -v 65000000                                                                                                                                  
bash: ulimit: virtual memory: cannot modify limit: Operation not permitted                                                                              
~> ulimit -v unlimited
bash: ulimit: virtual memory: cannot modify limit: Operation not permitted 

一些更多的搜索显示,原则上应该可以通过“as”(地址空间)条目设置这些限制 /etc/security/limits.conf。但是,通过这样做,我只能这样做 减少 最大的虚拟内存量,不是 增加 它。

有没有办法完全解除每个进程的虚拟内存限制,或者将其增加到超过64 GB?我想在一个应用程序中使用所有物理内存。

编辑:

  • 在Ingo Leonhardt之后,我试过了 ulimits -v unlimited 以root身份登录后,而不是标准用户。这样做可以解决root的问题(程序可以在以root用户身份登录时分配所有物理内存)。但这仅适用于root,不适用于其他用户。但是,至少这意味着原则上内核可以很好地处理这个问题,并且只存在配置问题。

  • 关于 limits.conf:我试过明确添加

    • 努力无限
    • 软无限

    /etc/security/limits.conf,并重新启动。这没有效果。以标准用户身份登录后, ulimit -v 仍然返回大约32 GB,和 ulimit -v 65000000 仍然说 permission denied (而 ulimit -v 64000000 作品)。其余的 limits.conf 被注释掉了 /etc/security/limits.d 只有一个不相关的条目(限制 nproc 非root用户为4096)。也就是说,虚拟内存限制必须来自其他地方 limits.conf。任何想法还有什么可以导致的 ulimits -v 不是“无限”?

编辑/解决方案:

  • 这是我自己的愚蠢造成的。我的用户设置中有一个(很久就被遗忘的)程序 setrlimit 限制每个进程的内存量,以防止Linux交换死亡。它无意中从32 GB机器复制到128 GB机器。感谢Paul和Andrew Janke以及其他所有人帮助追踪它。对不起大家:/。

  • 如果有人遇到这个:搜索 ulimit/setrlimit 在bash和配置文件设置中,以及可能调用它们的程序(包括您自己和系统范围的/ etc设置)并确保 /security/limits.conf 不包括此限制...(或者至少尝试创建新用户,以查看是否在您的用户或系统设置中发生这种情况)


7123
2018-05-11 16:40


起源

如果有人想在没有拥有128GB ram机器的情况下玩这款游戏,请访问Amazon EC2, r3.4xlarge 有122GB。虽然零售价为1.30美元/小时,但尚未检查现货市场。 - Paul
可能相关: stackoverflow.com/questions/8799481/... - Paul
我不认为C有 std::cout... - crashmstr
试着打电话 ulimit 作为根。至少两者 ulimit -v 65000000 和 ulimit -v unlimited 应该成功 - Ingo Leonhardt
@cgk当你这样做,你重启或只注销/登录?什么是 ulimit -v 什么时候跑进来 /etc/rc.local 自动启动(不是由您手动运行)?你可以编辑 ulimit -v >/tmp/ulimit.out 成 /etc/rc.local 以root为基础,通过查看来找到这个 /tmp/ulimit.out 将创建的文件。这是尝试查看它是否在init上设置并逐渐减少,或者是否在登录时设置了它。 - Paul


答案:


这是一个ulimit和系统设置问题,而不是c ++问题。

我可以在Amazon EC2实例类型上运行适当修改的代码 r3.4xlarge 没问题。这些在现货市场的成本不到0.20美元/小时,所以我建议你租一个,或者在/ etc中查看并与你自己的设置进行比较......或者你可能需要重新编译Linux内核才能使用它很多记忆...但它不是C ++或gcc问题。

EC2机器上的Ubuntu已经设置为无限制的进程内存。

$ sudo su
# ulimit -u
--> unlimited

这个有125GB的内存

# free
             total       used       free     shared    buffers     cached
Mem:     125903992    1371828  124532164        344      22156     502248
-/+ buffers/cache:     847424  125056568
Swap:            0          0          0

我修改了程序的限制,最高可达149GB。

这是输出。看起来很好,高达118GB。

root@ip-10-203-193-204:/home/ubuntu# ./memtest
allocation of 1 x 25 GB of data. Ok? yes
allocation of 1 x 26 GB of data. Ok? yes
allocation of 1 x 27 GB of data. Ok? yes
allocation of 1 x 28 GB of data. Ok? yes
allocation of 1 x 29 GB of data. Ok? yes
allocation of 1 x 30 GB of data. Ok? yes
allocation of 1 x 31 GB of data. Ok? yes
allocation of 1 x 32 GB of data. Ok? yes
allocation of 1 x 33 GB of data. Ok? yes
allocation of 1 x 34 GB of data. Ok? yes
allocation of 1 x 35 GB of data. Ok? yes
allocation of 1 x 36 GB of data. Ok? yes
allocation of 1 x 37 GB of data. Ok? yes
allocation of 1 x 38 GB of data. Ok? yes
allocation of 1 x 39 GB of data. Ok? yes
allocation of 1 x 40 GB of data. Ok? yes
allocation of 1 x 41 GB of data. Ok? yes
allocation of 1 x 42 GB of data. Ok? yes
allocation of 1 x 43 GB of data. Ok? yes
allocation of 1 x 44 GB of data. Ok? yes
allocation of 1 x 45 GB of data. Ok? yes
allocation of 1 x 46 GB of data. Ok? yes
allocation of 1 x 47 GB of data. Ok? yes
allocation of 1 x 48 GB of data. Ok? yes
allocation of 1 x 49 GB of data. Ok? yes
allocation of 1 x 50 GB of data. Ok? yes
allocation of 1 x 51 GB of data. Ok? yes
allocation of 1 x 52 GB of data. Ok? yes
allocation of 1 x 53 GB of data. Ok? yes
allocation of 1 x 54 GB of data. Ok? yes
allocation of 1 x 55 GB of data. Ok? yes
allocation of 1 x 56 GB of data. Ok? yes
allocation of 1 x 57 GB of data. Ok? yes
allocation of 1 x 58 GB of data. Ok? yes
allocation of 1 x 59 GB of data. Ok? yes
allocation of 1 x 60 GB of data. Ok? yes
allocation of 1 x 61 GB of data. Ok? yes
allocation of 1 x 62 GB of data. Ok? yes
allocation of 1 x 63 GB of data. Ok? yes
allocation of 1 x 64 GB of data. Ok? yes
allocation of 1 x 65 GB of data. Ok? yes
allocation of 1 x 66 GB of data. Ok? yes
allocation of 1 x 67 GB of data. Ok? yes
allocation of 1 x 68 GB of data. Ok? yes
allocation of 1 x 69 GB of data. Ok? yes
allocation of 1 x 70 GB of data. Ok? yes
allocation of 1 x 71 GB of data. Ok? yes
allocation of 1 x 72 GB of data. Ok? yes
allocation of 1 x 73 GB of data. Ok? yes
allocation of 1 x 74 GB of data. Ok? yes
allocation of 1 x 75 GB of data. Ok? yes
allocation of 1 x 76 GB of data. Ok? yes
allocation of 1 x 77 GB of data. Ok? yes
allocation of 1 x 78 GB of data. Ok? yes
allocation of 1 x 79 GB of data. Ok? yes
allocation of 1 x 80 GB of data. Ok? yes
allocation of 1 x 81 GB of data. Ok? yes
allocation of 1 x 82 GB of data. Ok? yes
allocation of 1 x 83 GB of data. Ok? yes
allocation of 1 x 84 GB of data. Ok? yes
allocation of 1 x 85 GB of data. Ok? yes
allocation of 1 x 86 GB of data. Ok? yes
allocation of 1 x 87 GB of data. Ok? yes
allocation of 1 x 88 GB of data. Ok? yes
allocation of 1 x 89 GB of data. Ok? yes
allocation of 1 x 90 GB of data. Ok? yes
allocation of 1 x 91 GB of data. Ok? yes
allocation of 1 x 92 GB of data. Ok? yes
allocation of 1 x 93 GB of data. Ok? yes
allocation of 1 x 94 GB of data. Ok? yes
allocation of 1 x 95 GB of data. Ok? yes
allocation of 1 x 96 GB of data. Ok? yes
allocation of 1 x 97 GB of data. Ok? yes
allocation of 1 x 98 GB of data. Ok? yes
allocation of 1 x 99 GB of data. Ok? yes
allocation of 1 x 100 GB of data. Ok? yes
allocation of 1 x 101 GB of data. Ok? yes
allocation of 1 x 102 GB of data. Ok? yes
allocation of 1 x 103 GB of data. Ok? yes
allocation of 1 x 104 GB of data. Ok? yes
allocation of 1 x 105 GB of data. Ok? yes
allocation of 1 x 106 GB of data. Ok? yes
allocation of 1 x 107 GB of data. Ok? yes
allocation of 1 x 108 GB of data. Ok? yes
allocation of 1 x 109 GB of data. Ok? yes
allocation of 1 x 110 GB of data. Ok? yes
allocation of 1 x 111 GB of data. Ok? yes
allocation of 1 x 112 GB of data. Ok? yes
allocation of 1 x 113 GB of data. Ok? yes
allocation of 1 x 114 GB of data. Ok? yes
allocation of 1 x 115 GB of data. Ok? yes
allocation of 1 x 116 GB of data. Ok? yes
allocation of 1 x 117 GB of data. Ok? yes
allocation of 1 x 118 GB of data. Ok? yes
allocation of 1 x 119 GB of data. Ok? nope
allocation of 1 x 120 GB of data. Ok? nope
allocation of 1 x 121 GB of data. Ok? nope
allocation of 1 x 122 GB of data. Ok? nope
allocation of 1 x 123 GB of data. Ok? nope
allocation of 1 x 124 GB of data. Ok? nope
allocation of 1 x 125 GB of data. Ok? nope
allocation of 1 x 126 GB of data. Ok? nope
allocation of 1 x 127 GB of data. Ok? nope
allocation of 1 x 128 GB of data. Ok? nope
allocation of 1 x 129 GB of data. Ok? nope
allocation of 1 x 130 GB of data. Ok? nope
allocation of 1 x 131 GB of data. Ok? nope
allocation of 1 x 132 GB of data. Ok? nope
allocation of 1 x 133 GB of data. Ok? nope
allocation of 1 x 134 GB of data. Ok? nope
allocation of 1 x 135 GB of data. Ok? nope
allocation of 1 x 136 GB of data. Ok? nope
allocation of 1 x 137 GB of data. Ok? nope
allocation of 1 x 138 GB of data. Ok? nope
allocation of 1 x 139 GB of data. Ok? nope
allocation of 1 x 140 GB of data. Ok? nope
allocation of 1 x 141 GB of data. Ok? nope
allocation of 1 x 142 GB of data. Ok? nope
allocation of 1 x 143 GB of data. Ok? nope
allocation of 1 x 144 GB of data. Ok? nope
allocation of 1 x 145 GB of data. Ok? nope
allocation of 1 x 146 GB of data. Ok? nope
allocation of 1 x 147 GB of data. Ok? nope
allocation of 1 x 148 GB of data. Ok? nope
allocation of 1 x 149 GB of data. Ok? nope

现在,我在这上花了0.17美元......


9
2018-05-11 17:36



很有意思。几乎和OP计划用128 GB内存一样有趣。 - Carlton
@Carlton另一个有趣的问题是,为什么人们对有保证的虚拟机收费如此之多,而不是可能会消失的现有虚拟机。让一个人进入另一个人是如此困难吗? - Paul
@Paul肯定。如果你想跳过那些篮球,就去做吧。它将有开发成本。构建故障转移系统需要多少小时的开发成本才能为每个“大型”CPU群每小时节省1美元?取决于您租用多少小时的“大型”CPU集群。 - Yakk - Adam Nevraumont
@cgk我注意到我全新安装的64位Ubuntu 15.04具有无限的ulimit。也许您需要拉出主硬盘驱动器,将它们放在一边,弹出另一个驱动器,然后从DVD或USB棒重新安装。我玩过 ulimit 命令,并注意到它 由bash定义。 ulimit 它不是文件系统中可执行的命令,它在 bash,它还有一个联机帮助页 弃用 sysFall在C.From shell中, help ulimit 即使是root,我也无法设置硬限制 ulimit -H -v [number of kB]。我可以设置和撤消软限制作为root。建议你尝试重新安装。 - Paul
我相信更新的POSIX系统调用来取代 ulimit 是 setrlimit/getrlimit。 pubs.opengroup.org/onlinepubs/9699919799/functions/...。我不知道他们为Fedora配置了默认设置,但也许这是一个领先优势。 - Andrew Janke