[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VM cache policy change
From: |
Justus Winter |
Subject: |
Re: VM cache policy change |
Date: |
Tue, 24 Feb 2015 17:15:22 +0100 |
User-agent: |
alot/0.3.5 |
Quoting Samuel Thibault (2015-02-24 01:04:19)
> I tried to start a gcc-5 build, it gets stuck at the tar x stage, with
> gnumach printing:
>
> no more room for vm_map_find_entry in 80223e20 (kmem_map_store)
> no more room for kmem_realloc in 80223e20 (kmem_map_store)
>[...]
> ipc_port 0010 80 4k 50 262239 262350 20988k
> 0k
kmem_realloc is only used to enlarge the ipc tables, but this is not
due to the lack of space, but due to the lack of a sufficiently large
continuous chunk of the kernel address space.
As demonstrated by the attached program the maximum number of ports a
task can have seems to be around 250000, which doesn't seem like a
lot.
% ./test
./test: mach_port_allocate (last good name: 242175): (os/kern) resource shortage
This suggests that we need a different data structure that doesn't
depend on a continuous chunk of memory.
Justus
test.c
Description: Text Data
- VM cache policy change, Justus Winter, 2015/02/21
- [PATCH gnumach 1/3] VM cache policy change, Justus Winter, 2015/02/21
- [PATCH gnumach 3/3] vm: evict clean pages first, Justus Winter, 2015/02/21
- [PATCH gnumach 2/3] vm: keep track of clean pages, Justus Winter, 2015/02/21
- Re: VM cache policy change, Samuel Thibault, 2015/02/22
- Re: VM cache policy change, Richard Braun, 2015/02/22