diff options
| author | avg <avg@FreeBSD.org> | 2010-09-17 07:36:32 +0000 |
|---|---|---|
| committer | avg <avg@FreeBSD.org> | 2010-09-17 07:36:32 +0000 |
| commit | eb6f40cd9bddd8ed6b70f38f36f4c25b3b68c574 (patch) | |
| tree | f261f3800e90534cef1298b404166f02e48bb5d0 /sys/amd64/include/vmparam.h | |
| parent | c133aaf44557abcbae8095a0cfd4a5940ba4ae5c (diff) | |
| download | FreeBSD-src-eb6f40cd9bddd8ed6b70f38f36f4c25b3b68c574.zip FreeBSD-src-eb6f40cd9bddd8ed6b70f38f36f4c25b3b68c574.tar.gz | |
amd64: reduce VM_KMEM_SIZE_SCALE to 1 allowing kernel to use more memory
KVA space is abundant on amd64, so there is no reason to limit kernel
map size to a fraction of available physical memory. In fact, it could
be larger than physical memory.
This should help with memory auto-tuning for ZFS and shouldn't affect
other workloads.
This should reduce number of circumstances for "kmem_map too small"
panics, but probably won't eliminate them entirely due to potential kmem
fragmentation.
In fact, you might want/need to limit maximum ARC size after this commit
if you need to resrve more memory for applications.
This change was discussed on arch@ and nobody said "don't do it".
MFC after: 6 weeks
Diffstat (limited to 'sys/amd64/include/vmparam.h')
| -rw-r--r-- | sys/amd64/include/vmparam.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/amd64/include/vmparam.h b/sys/amd64/include/vmparam.h index f86b184..dd0c0c9 100644 --- a/sys/amd64/include/vmparam.h +++ b/sys/amd64/include/vmparam.h @@ -205,7 +205,7 @@ * is the total KVA space allocated for kmem_map. */ #ifndef VM_KMEM_SIZE_SCALE -#define VM_KMEM_SIZE_SCALE (3) +#define VM_KMEM_SIZE_SCALE (1) #endif /* |
