Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: kumagai-atsushi@mxc.nes.nec.co.jp, d.hatayama@jp.fujitsu.com,
	kexec@lists.infradead.org
Subject: Re: [PATCH 1/2 V2] raw i/o and root device to use less memory
Date: Mon, 13 Jan 2014 16:02:05 +0100	[thread overview]
Message-ID: <20140113160205.6e631a5e@holzheu> (raw)
In-Reply-To: <20140113133033.GA917@sgi.com>

On Mon, 13 Jan 2014 07:30:33 -0600
Cliff Wickman <cpw@sgi.com> wrote:

> On Mon, Jan 13, 2014 at 10:58:31AM +0100, Michael Holzheu wrote:
> > On Fri, 10 Jan 2014 11:58:30 -0600
> > Cliff Wickman <cpw@sgi.com> wrote:
> > 
> > [snip]
> > 
> > > Use O_DIRECT (raw) i/o for the dump and for the bitmaps file, so that writing
> > > to those files does not allocate kernel memory for page cache.
> > 
> > Hello Cliff,
> > 
> > Have you tested O_DIRECT together with the new vmcore mmap interface?
> > IIRC when we tried O_DIRECT together with mmap for some reason it did
> > not work.
> > 
> > Michael
> 
> Hi Michael,
> 
>   How new of a kernel do I need?  i.e. how 'new' of an mmap interface?
>   The latest kernel I used was 3.0.93 (sle11sp3).
>   And makedumpfile was 1.5.5.

I think sles11 SP3 does not support mmap for /proc/vmcore. Upstream you
need at least kernel 3.11. For makedumpfile version 1.5.5 should be ok.

Michael


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

  reply	other threads:[~2014-01-13 15:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 23:30 [PATCH 0/2] makedumpfile: for large memories cpw
2013-12-31 23:34 ` [PATCH 1/2] makedumpfile: raw i/o and use of root device Cliff Wickman
2013-12-31 23:36 ` [PATCH 2/2] makedumpfile: exclude unused vmemmap pages Cliff Wickman
2014-01-06  9:27 ` [PATCH 0/2] makedumpfile: for large memories Atsushi Kumagai
2014-01-09  0:25   ` Cliff Wickman
2014-01-10  7:48     ` Atsushi Kumagai
2014-01-10 18:23       ` Cliff Wickman
2014-01-14 12:59         ` HATAYAMA Daisuke
2014-01-07 10:14 ` HATAYAMA Daisuke
2014-01-10 17:58 ` [PATCH 1/2 V2] raw i/o and root device to use less memory Cliff Wickman
2014-01-13  9:58   ` Michael Holzheu
2014-01-13 13:30     ` Cliff Wickman
2014-01-13 15:02       ` Michael Holzheu [this message]
2014-01-10 18:00 ` [PATCH 2/2 V2] exclude unused vmemmap pages Cliff Wickman
2014-01-14 11:33 ` [PATCH 0/2] makedumpfile: for large memories HATAYAMA Daisuke

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=20140113160205.6e631a5e@holzheu \
    --to=holzheu@linux.vnet.ibm.com \
    --cc=cpw@sgi.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    /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