All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Kexec Mailing List <kexec@lists.infradead.org>,
	Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: Arthur Zou <zzou@redhat.com>
Subject: makedumpfile memmory usage seems high with option -E
Date: Thu, 10 Apr 2014 17:44:33 -0400	[thread overview]
Message-ID: <20140410214433.GF18808@redhat.com> (raw)

Hi Atsushi/Hatayama,

We noticed in our testing that makedumpfile gets OOM killed if we happen
to use -E option. Saving to compressed kdump format works just fine.

Also we noticed that with -E if we disable cyclic mode then it works just
fine.

So looks like something is going on with -E and cyclic mode enabled. I am
not sure what it is.

Do you suspect something?

Thanks
Vivek

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

             reply	other threads:[~2014-04-10 21:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 21:44 Vivek Goyal [this message]
2014-04-11  9:22 ` makedumpfile memmory usage seems high with option -E Atsushi Kumagai
2014-04-11 10:19   ` Arthur Zou
2014-04-14  8:02     ` [PATCH] makedumpfile: change the wrong code to calculate bufsize_cyclic for elf dump Baoquan He
2014-04-14  8:11       ` Baoquan He
2014-04-16  6:44       ` Baoquan He
2014-04-17  4:01         ` Atsushi Kumagai
2014-04-17  4:52           ` bhe
2014-04-17  5:02             ` bhe
2014-04-18  9:22               ` Atsushi Kumagai
2014-04-18 14:29                 ` bhe
2014-04-18 19:41                   ` Petr Tesarik
2014-04-21 15:19                     ` Vivek Goyal
2014-04-21 15:46                       ` Petr Tesarik
2014-04-21 15:51                         ` Vivek Goyal
2014-04-21 15:14                   ` Vivek Goyal
2014-04-23 11:09                     ` bhe
2014-04-21 15:12                 ` Vivek Goyal
2014-04-23  7:55                   ` Atsushi Kumagai
2014-04-23 11:55                     ` bhe
2014-04-23 17:08                     ` Vivek Goyal
2014-04-23 23:50                       ` bhe
2014-04-24  2:05                         ` bhe
2014-04-25 13:22                         ` Vivek Goyal
2014-04-28  5:05                           ` Atsushi Kumagai
2014-04-28 12:50                             ` Vivek Goyal
2014-05-09  5:36                               ` Atsushi Kumagai
2014-05-09 20:49                                 ` Vivek Goyal
2014-05-15  7:22                                   ` bhe
2014-05-15  9:10                                     ` Atsushi Kumagai
2014-05-19 11:15                                       ` bhe
2014-05-19 15:11                                         ` Vivek Goyal
2014-05-27  5:34                                           ` Atsushi Kumagai
2014-05-27 14:49                                             ` Vivek Goyal
2014-05-23  7:18                                         ` Atsushi Kumagai
2014-05-14  5:44                                 ` bhe
2014-04-28  5:04                       ` Atsushi Kumagai
2014-05-09  5:35                         ` Atsushi Kumagai

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=20140410214433.GF18808@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=zzou@redhat.com \
    /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.