on 28/05/2010 16:45 Jeremy Chadwick said the following:
> It is? On amd64, vm.kmem_size (not vm.kmem_size_max) is what has to be
> increased. I can point folks to the "official" statement from pjd@ and
> some others if need be. For a very long time I questioned this because
> for an even longer amount of time we were being told to increase
> vm.kmem_size_max, by default, is already huge on amd64 (~320GB or
> something like that). Proof:
> vm.kmem_size_max: 329853485875
> To the OP: you will need to increase vm.kmem_size in /boot/loader.conf
> and reboot the system. "What value do I pick?" With 4GB, I would
> recommend you use these two variables:
> This will increase the available kmem, and also limit the ARC size
> explicitly to nothing larger than 1.5GB. This should stabilise your
you are correct, I was confused about what kmem_size_max and kmem_size meant.
kmem_size_max is what could be available, in principle, for kmem_map.
But in practice kmem_map size is auto-set to about 1/3 of physical memory
available, this is on amd64.
BTW, the "6GB" change you mentioned in your other email was more relevant to
kmem_size_max, it was overridden since then with 512GB change.
kmem size calculations are very well explained here:
BTW, I don't see why we set kmem size to a fraction of physical memory on amd64
where we have plenty of KVM available. I don't buy the argument that larger
size would allow kernel to exhaust all physical memory which would lead to a
thing", e.g. a panic - right now kernel can exhaust all kmem which does lead to
Perhaps, default value of VM_KMEM_SIZE_SCALE should be change to one on amd64?
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"