On Fri, Oct 28, 2005 at 08:48:55AM -0400, Tamas K Papp wrote: > On Fri, Oct 28, 2005 at 09:32:15PM +1000, Benjamin Herrenschmidt wrote: > > > > > Actually, if you don't want to take the perfs. hit caused by > > > > CONFIG_HIGHMEM, you can also play around with TASK_SIZE and KERNELBASE > > > > values in the .config :) But if you don't know what it's all about, then > > > > don't even try ! Besides, it will break yaboot. > > > > > > Benh, do you know how much the performance hit is ? > > > > Nope. Never actually measured :) > > Ben and Sven, > > I did not make any precise and measurements, but I am running > numerically intensive algorithms (MCMC and approximate dynamic > programming, they use quite a bit of memory too) which I time. I > compared the log files with the ones before HIGHMEM kernels, and I see > no change in performance that is outside the range of measurement > error.
Cool, because we set those options in the debian kernels, and i wondered if i should have started playing with TASK_SIZE and KERNELBASE. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
