All of lore.kernel.org
 help / color / mirror / Atom feed
From: tachibana@mxm.nes.nec.co.jp
To: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: tachibana@mxm.nes.nec.co.jp,
	Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	Kexec-ml <kexec@lists.infradead.org>,
	Ananth Narayan <ananth@in.ibm.com>,
	Reinhard <BUENDGEN@de.ibm.com>
Subject: Re: [PATCH] makedumpfile: s390x: Auto-detect the correct MAX_PHYSMEM_BITSusedin vmcore being analyzed.
Date: Wed, 21 Dec 2011 21:48:09 +0900	[thread overview]
Message-ID: <20111221214809tachibana@mail.jp.nec.com> (raw)
In-Reply-To: <4EF1B019.3030201@linux.vnet.ibm.com>

Hi Mahesh,

On 2011/12/21 15:38:25 +0530, Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com> wrote:
> On 12/21/2011 11:41 AM, tachibana@mxm.nes.nec.co.jp wrote:
> > Hi Mahesh,
> > 
> > Thank you for the patch.
> > I will review it.
> > However I have never dumped 1 terabyte or more data using makedumpfile.
> > Has anyone ever dumped it successfully?
> > 
> 
> I have seen makedumpfile successfully compressing vmcore generated on
> system with 1TB memory.

Thank you for your information.

Thanks.
tachibana

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

  reply	other threads:[~2011-12-22  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 10:36 [PATCH] makedumpfile: s390x: Auto-detect the correct MAX_PHYSMEM_BITS used in vmcore being analyzed Mahesh J Salgaonkar
2011-12-20 13:21 ` Michael Holzheu
2011-12-21  6:11 ` [PATCH] makedumpfile: s390x: Auto-detect the correct MAX_PHYSMEM_BITSused " tachibana
2011-12-21 10:08   ` Mahesh Jagannath Salgaonkar
2011-12-21 12:48     ` tachibana [this message]
2012-01-17  4:40       ` [PATCH] makedumpfile: s390x: Auto-detect the correct MAX_PHYSMEM_BITSusedin " 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=20111221214809tachibana@mail.jp.nec.com \
    --to=tachibana@mxm.nes.nec.co.jp \
    --cc=BUENDGEN@de.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=mahesh@linux.vnet.ibm.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.