Date: Sun, 09 Dec 2012 14:41:14 +0100 From: rank1seeker@gmail.com To: hackers@freebsd.org, alc@freebsd.org, avg@freebsd.org, davide@freebsd.org Subject: Re: huge ktr buffer Message-ID: <20121209.134114.135.1@DOMY-PC> In-Reply-To: <CACYV=-HhQcPx4nM=Ytc3wKS-oZqvtZCquJZSL6BooDHvRpuvGA@mail.gmail.com> References: <50C0B763.8000004@FreeBSD.org> <CACYV=-HhQcPx4nM=Ytc3wKS-oZqvtZCquJZSL6BooDHvRpuvGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> As also Alan suggested, a way to workaround the problem is to increase
> NKPT value (e.g. from 32 to 64). Obviously, this is not a proper fix.
> For a proper fix the kernel needs to be able to dynamically set the
> size of NKPT. In this particular case, this wouldn't be too hard, but
> there is a different case, where people preload a large memory disk
> image at boot time that isn't so easy to fix.
>
> Thanks,
>
> Davide
Had a same issue.
I use very big preloaded images, with full world + many compiled ports in it.
Fix:
'sh' code snip ...
----
# Get default NKTP value
nkpt=`cat "/sys/$arch/include/pmap.h" | sed -En 's/.+NKPT[[:blank:]]+([0-9]{2})$/\1/p'`
# How many additional NKPT (4 Mb each), for our image, added to amount of NKPT?
# Calculated in Kb
: $((nkpt += "$img_size" / 4096))
----
But it loads sooooo slow into the RAM.
That should be enhanced, too.
Domagoj Smolčić
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121209.134114.135.1>