All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: kexec@lists.infradead.org
Subject: problems in kdump kernel if 'maxcpus=1' not specified?
Date: Tue, 15 Jul 2008 18:07:40 -0700	[thread overview]
Message-ID: <487D49DC.8040209@sgi.com> (raw)

Are there known problems if you boot up kdump kernel with
multipl cpus?

It takes unacceptably long time to run makedumpfile in
saving dump at a huge memory system. In my testing it
took 16hr25min to run create_dump_bitmap() on a 1TB system.
Pfn's are processed sequentially with single cpu. We
certainly can use multipl cpus here ;)

Regards,
 - jay

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2008-07-16  1:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  1:07 Jay Lan [this message]
2008-07-16 15:12 ` problems in kdump kernel if 'maxcpus=1' not specified? 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

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=487D49DC.8040209@sgi.com \
    --to=jlan@sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.