From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: problems in kdump kernel if 'maxcpus=1' not specified?
Date: Wed, 16 Jul 2008 18:45:32 +0200 [thread overview]
Message-ID: <20080716184532.4ee555e2@halley.suse.de> (raw)
In-Reply-To: <20080716163404.GD711@redhat.com>
* Vivek Goyal [2008-07-16 12:34]:
>
> 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?
No, the whole system memory mappend (beside of boot memory) beyond
1^32. Like (from /proc/iomem):
6000100000-60003fffff : System RAM
6003000000-6033dfffff : System RAM
6033e00000-6043ffffff : System RAM
6044000000-6045b9efff : System RAM
6045b9f000-60f7ffdfff : System RAM
16000100000-160003fffff : System RAM
16003000000-16033dfffff : System RAM
...
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2008-07-16 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 1:07 problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:12 ` Vivek Goyal
2008-07-16 15:25 ` Neil Horman
2008-07-16 16:23 ` Vivek Goyal
2008-07-16 17:03 ` Neil Horman
2008-07-16 19:16 ` Jay Lan
2008-07-17 4:59 ` Ken'ichi Ohmichi
2008-07-17 6:35 ` [PATCH] makedumpfile: Shrink the time for creating 1st-bitmap (Re: problems in kdump kernel if 'maxcpus=1' not specified?) Ken'ichi Ohmichi
2008-07-17 17:09 ` Jay Lan
2008-07-18 4:00 ` Ken'ichi Ohmichi
2008-07-18 15:57 ` Jay Lan
2008-07-16 18:00 ` problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:26 ` Bernhard Walle
2008-07-16 16:34 ` Vivek Goyal
2008-07-16 16:45 ` Bernhard Walle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080716184532.4ee555e2@halley.suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox