* Vasiliy Kiryanov <vasiliy.kiryanov@gmail.com> [2010-02-18 18:08]:
quoted text
> Hello Community.
> 
> There are 2 parameters that I would want to understand better and trace somehow:
> MAX_KMAPENT, and NKMEMPAGES.

they don't really matter any more.

quoted text
> notice:
> I have found only one source of such info:
> "Running and tuning OpenBSD network server in a production
> environment" (Oct 8, 2002)
> http://www.openbsd.org/papers/tuning-openbsd.ps

this is 99% irrelevant these days.

quoted text
> I have rebuilt kernel with following values:
> option NKMEMPAGES=32768
> option MAX_KMAPENT=3072
> 
> MAX_KMAPENT check:
> # vmstat -s
> 6179 kernel map entries (how can it be more then 3072 ?)
> 
> 
> NKMEMPAGES check:
> # vmstat -m
> Memory resource pool statistics
> Name        Size Requests Fail    InUse Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
> mbpl         256 189887305   0     1239   499    32   467   467     1   384  353
> mcl2k       2048 1414599843  0      521  1857     0  1857  1857     4  3072 1590
> 
> People often write that we can find some correlation between these
> params and NKMEMPAGES.
> I can't find any correlation here, so any hints are welcome.

you are not only randmly pushing buttons you don't understand, you
also ended up pushing the wrong ones.
the mbuf related pools these days are 1) way bigger by default than
they used to be, and rarely need any adjustment at all and 2) the
relevant one (mbuf cluster pool, mcl2k) grows on demand up to the
value in sysctl kern.maxclusters.

-- 
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting