From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Travis Date: Wed, 09 Dec 2009 18:37:16 +0000 Subject: Re: [PATCH] mm/vmalloc: don't use vmalloc_end Message-Id: <4B1FEE5C.1030303@sgi.com> List-Id: References: <4B1D3A3302000078000241CD@vpn.id2.novell.com> <20091207153552.0fadf335.akpm@linux-foundation.org> <4B1E1B1B0200007800024345@vpn.id2.novell.com> <4B1FE81F.30408@sgi.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christoph Lameter Cc: tony.luck@intel.com, Andrew Morton , Jan Beulich , Tejun Heo , linux-mm@kvack.org, Geert Uytterhoeven , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Christoph Lameter wrote: > On Wed, 9 Dec 2009, Mike Travis wrote: > >>> Tony: Can you confirm that the new percpu stuff works on IA64? (Or is >>> there nobody left to care?) >> Christoph, I have access to a 640p system for a couple more weeks if >> there's anything you'd like me to check out. > > Boot with 2.6.32 and see if the per cpu allocator works. Check if there > are any changes to memory consumption. Create a few thousand virtual > ethernet devices and see if the system keels over. Any advice on how to go about the above would be helpful... ;-) > > It may also be good to run some scheduler test. Compare AIM9 of latest > SLES with 2.6.32. Concurrent page fault test? Then a performance test with > lots of concurrency but the usual stuff wont work since HPC apps usually > pin. I'm doing some aim7/9 comparisons right now between SPARSE and DISCONTIG memory configs using sles11 + 2.6.32. Which other benchmarks would you recommend for the other tests? > > Run latencytest (available in the lldiag package) from > kernel.org/pub/linux/kernel/people/christoph/lldiag and see how the > disturbances by the OS are changed. I'll put that on the list.