Date: Wed, 25 Jun 2003 22:02:41 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: "Cagle, John (ISS-Houston)" <john.cagle@hp.com> Cc: current@freebsd.org Subject: Re: Best way to get max KVA setting? Message-ID: <3EFA7E71.75919A7E@mindspring.com> References: <C50AB9511EE59B49B2A503CB7AE1ABD10440E578@cceexc19.americas.cpqcorp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Cagle, John (ISS-Houston)" wrote: > Terry Lambert [mailto:tlambert2@mindspring.com] > > Mike Silbersack wrote: > > > I could probably grep for this, but what's the best way to get a hold > > > of the # of pages (or MB of ram) that max KVA is set to? I'm adding > > > another autosize option, and I want to base it on min (KVA, ram) so > > > that it doesn't balloon on boxes where ram >> KVA. > > > > I posted a patch about a month ago that did exactly this. > > > > It was for a guy who was was running with PAE enabled on an > > 8G machine, and the autotuning was shooting him in the foot when it > > tried to grab enough memory to create kmem_map entries for the 8G of RAM > > in his 2G KVA space, and its head exploded. > > I'm that guy who was running PAE on an 8GB machine... > > BTW, it turns out the problem was _not_ the autotuning, it was simply an > overflow of a 32-bit variable in the kernel. It's been fixed in > -current, checked in 2 weeks ago. I still expect that there are issues with the autotuning not taking KVA << RAM into account, without something like my patch, even if it's not biting you specifically at 8G. I'd like to see what happens at 64G RAM, for example... In any case, the patch I posted is still probably what Mike wanted. 8-). -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EFA7E71.75919A7E>