Date: Mon, 13 Aug 2012 12:03:11 -0500 From: Alan Cox <alan.l.cox@gmail.com> To: Colin Percival <cperciva@freebsd.org> Cc: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? Message-ID: <CAJUyCcPM72COH-u24tdFYA5MH7yCQct4qsccGe7X4xo3GGmxhA@mail.gmail.com> In-Reply-To: <502831B7.1080309@freebsd.org> References: <502831B7.1080309@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 12, 2012 at 5:44 PM, Colin Percival <cperciva@freebsd.org>wrote: > Hi all, > > If I'm understanding things correctly, the "maxswzone" value -- set by the > kern.maxswzone loader tunable or to VM_SWZONE_SIZE_MAX by default -- should > be approximately 9 MiB per GiB of swap space. > > The current default for VM_SWZONE_SIZE_MAX was set in August 2002 to 32 > MiB; > meaning that anyone who wants to use more than ~ 3.5 GB of swap space ought > to set kern.maxswzone in /boot/loader.conf. > > Is it time to increase this default on amd64? (I understand that keeping > the > value low on i386 is important due to KVA limitations, but amd64 has far > more > address space available...) > > The short answer is "Yes." The long answer is that amd64, ia64, etc. shouldn't have this limit at all. The swap zone objects are small objects that could be allocated by uma_small_alloc() and accessed through the direct map. Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJUyCcPM72COH-u24tdFYA5MH7yCQct4qsccGe7X4xo3GGmxhA>