This is a discussion on Re: kmem_map too small - FreeBSD ; =D0=92 =D0=9F=D1=82, 16/11/2007 =D0=B2 09:16 +0100, Kris Kennaway =D0=BF=D0= =B8=D1=88=D0=B5=D1=82: > Check the archives, this comes up a lot (you need to increase the amount=20 > of memory allocated to the kernel). Already did. The question actually is how much ...
=D0=92 =D0=9F=D1=82, 16/11/2007 =D0=B2 09:16 +0100, Kris Kennaway =D0=BF=D0=
> Check the archives, this comes up a lot (you need to increase the amount=20
> of memory allocated to the kernel).
The question actually is how much memory I should allocate for
kernel (exactly, what numbers should be placed into /boot/loader.conf in
vm.kmem_size and vm.kmem_size_max) and what amount of kernel memory
depends on and how I could calculate kernel memory needs.
Trivial answer "just try to experiment" is not definitely enough.
First of all, this process can be _extremely_ lengthy: about two months
ago I have tried to "brute force" guess vm.kmem* values to start using
ZFS on my desktop at work: two weeks for testing is very large amount of
time, and, as said by Dijkstra, "testing can only show us presence of
bugs, and not their absence": "cvs -z 5 -g up -P -d" done in /usr/ports
(very good test to crash your machine if you're using ZFS because of
heavy usage of ZFS POSIX name resolution cache) stopped crashing my box,
but I can't say that any other test will not crash it.
Second, the machine in question operates unattended, and our technical
support engineers are not qualified enough to tweak boot loader
parameters, as such, I should constantly monitor this server what I
don't wish to do.
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D 0=BC,
email@example.com mailing list
To unsubscribe, send any mail to "firstname.lastname@example.org"