Date: Mon, 15 Dec 2014 17:12:39 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Alfred Perlstein <bright@mu.org> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Ian Lepore <ian@freebsd.org>, Peter Wemm <peter@wemm.org> Subject: Re: i386 PAE kernel works fine on 10-stable Message-ID: <CAJ-VmokJ=%2BNwAfzoATzaiWD1RsbWeSbb07DLUeYKwCOSCzDuBg@mail.gmail.com> In-Reply-To: <A33FE253-B9EE-46FE-9229-CFBC21A80024@mu.org> References: <1418579278.2026.9.camel@freebsd.org> <1418580756.2026.12.camel@freebsd.org> <847BD158-0867-4F5F-83A9-1651E77D29EF@mu.org> <1641407.80FsgLC8bS@overcee.wemm.org> <A33FE253-B9EE-46FE-9229-CFBC21A80024@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 December 2014 at 16:33, Alfred Perlstein <bright@mu.org> wrote: > >> On Dec 15, 2014, at 3:42 PM, Peter Wemm <peter@wemm.org> wrote: >> >> It's always been a 1GB/3GB split. It was never a problem until certain >> scaling defaults were changed to scale solely based on physical ram without >> regard for kva limits. > > Hmm the original patch I gave for that only changed scaling for machines with 64 bit pointers. Why was it that the 32 bit stuff was made to change? I recall this - I went digging; commit 7beb738c8a72cc197d3e898784afe3fba28f1834 removed that particular bit of autotuning based on the size of void *. Maybe this stuff is a little busted and we need to add some more config parameters? (Also, there's the vm space shift thing that also needed adjustment for memory-constrained systems. We've had do it on MIPS and low-memory (64mb, 128mb) RAM i386 systems.) -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokJ=%2BNwAfzoATzaiWD1RsbWeSbb07DLUeYKwCOSCzDuBg>