problems in kdump kernel if 'maxcpus=1' not specified?
vgoyal at redhat.com
Wed Jul 16 12:34:04 EDT 2008
On Wed, Jul 16, 2008 at 05:26:01PM +0200, Bernhard Walle wrote:
> * Vivek Goyal [2008-07-16 11:12]:
> > You need to dive deeper to find out what is taking so much of time.
> I think the main difference are the huge memory gaps usual on IA64
> systems. makedumpfile processes each PFN sequentially when creating the
> 1st bitmap.
By memory gaps you mean large amount of memory? If yes, on 128GB system
it took me 4 min and on 1TB system (10 times memory), it takes 16hrs.
Almost 240 times the duration of 128GB. That sounds horrible.
Either it is some kind of NUMA machine and memory access to remote nodes is
really slow. I am not sure if that's the case.
More information about the kexec