All of lore.kernel.org
 help / color / mirror / Atom feed
From: dyoung@redhat.com
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: bhe@redhat.com, corbet@lwn.net, yinghai@kernel.org,
	akpm@linux-foundation.org, dyoung@redhat.com, vgoyal@redhat.com
Subject: [PATCH 0/3] kdump: crashkernel parameter improvement
Date: Tue, 24 Oct 2017 13:31:47 +0800	[thread overview]
Message-ID: <20171024053147.493545734@redhat.com> (raw)

Hi,

Here is a try to improve current crashkernel kernel parameter

Patch 1/3 adds an extra functionality so that one can use like
crashkernel=2G-:128M^12 to reserve 128M for 2G+ machine but also scale the
size based on system memory, that means 128M + (total_mem - 128M) >> 12

Patch 2/3 is a resending of previous post to let crashkernel=xM to reserve
first from below 896M, then <4G, then <MAXMEM

Patch 3/3 round up total system memory size because according to test the
mem size from memblock api is usually smaller than actual size, this passed
my tests on x86/arm/powerpc, it should work for most cases, but there might 
be exceptions, appreciated for any better idea.

Thanks
Dave


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

WARNING: multiple messages have this Message-ID (diff)
From: dyoung@redhat.com
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, bhe@redhat.com, vgoyal@redhat.com,
	yinghai@kernel.org, corbet@lwn.net, dyoung@redhat.com
Subject: [PATCH 0/3] kdump: crashkernel parameter improvement
Date: Tue, 24 Oct 2017 13:31:47 +0800	[thread overview]
Message-ID: <20171024053147.493545734@redhat.com> (raw)

Hi,

Here is a try to improve current crashkernel kernel parameter

Patch 1/3 adds an extra functionality so that one can use like
crashkernel=2G-:128M^12 to reserve 128M for 2G+ machine but also scale the
size based on system memory, that means 128M + (total_mem - 128M) >> 12

Patch 2/3 is a resending of previous post to let crashkernel=xM to reserve
first from below 896M, then <4G, then <MAXMEM

Patch 3/3 round up total system memory size because according to test the
mem size from memblock api is usually smaller than actual size, this passed
my tests on x86/arm/powerpc, it should work for most cases, but there might 
be exceptions, appreciated for any better idea.

Thanks
Dave

             reply	other threads:[~2017-10-24  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24  5:31 dyoung [this message]
2017-10-24  5:31 ` [PATCH 0/3] kdump: crashkernel parameter improvement dyoung

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=20171024053147.493545734@redhat.com \
    --to=dyoung@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=corbet@lwn.net \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@kernel.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.