Date: Tue, 24 Jan 2006 13:23:52 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Mark Tinguely <tinguely@casselton.net> Cc: m.lyubich@suzlon.de, freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, kris@obsecurity.org Subject: Re: Broadcomm BCM4401-B0 and memory upgrade issue. Message-ID: <20060124212352.GA53686@troutmask.apl.washington.edu> In-Reply-To: <200601242112.k0OLCHQs026935@casselton.net> References: <2BB1D847970ED7459EAA23DAB225073714FCE1@hrosvr02.suzlon.de> <200601242112.k0OLCHQs026935@casselton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 24, 2006 at 03:12:17PM -0600, Mark Tinguely wrote: > Have you tried to boot with the old contigmalloc using the sysctl > option "vm.old_contigmalloc=1"? Yes. This makes an enormous difference in boot up times. With vm.old_contigmalloc=1, fxp0 probes within a few seconds. Without it, fxp0 takes more than 7 minutes to probe. > Some people are seeing slow boot/configuration with new style > vm_page_alloc_contig/contigmalloc. yep. > I am doing some profiling of vm_page_alloc_contig() and have found > that larger physical memory configurations makes these problems much worse. yep. I have 12 GB. > I identified 4-5 places that can be changed to decrease the number > of page tables that is needed to be checked before an allocating a range. > Some of the changes will only occasionally save a few page checks, but > others changes could save several hundred or more page checks on every call. If you come up with a patch, I'm more than willing to test it. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060124212352.GA53686>