linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Pingfan Liu <kernelfans@gmail.com>
Cc: kexec@lists.infradead.org, Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCHv4] powerpc/crashkernel: take "mem=" option into account
Date: Tue,  9 Jun 2020 15:28:56 +1000 (AEST)	[thread overview]
Message-ID: <159168034259.1381411.9724380160125554368.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <1585749644-4148-1-git-send-email-kernelfans@gmail.com>

On Wed, 1 Apr 2020 22:00:44 +0800, Pingfan Liu wrote:
> 'mem=" option is an easy way to put high pressure on memory during some
> test. Hence after applying the memory limit, instead of total mem, the
> actual usable memory should be considered when reserving mem for
> crashkernel. Otherwise the boot up may experience OOM issue.
> 
> E.g. it would reserve 4G prior to the change and 512M afterward, if passing
> crashkernel="2G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G", and
> mem=5G on a 256G machine.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/crashkernel: Take "mem=" option into account
      https://git.kernel.org/powerpc/c/be5470e0c285a68dc3afdea965032f5ddc8269d7

cheers

      parent reply	other threads:[~2020-06-09  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 14:18 [PATCHv3] powerpc/crashkernel: take "mem=" option into account Pingfan Liu
2020-03-26  7:48 ` Hari Bathini
2020-04-01 14:00   ` [PATCHv4] " Pingfan Liu
2020-04-01 18:36     ` Hari Bathini
2020-06-09  5:28     ` Michael Ellerman [this message]

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=159168034259.1381411.9724380160125554368.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=hbathini@linux.ibm.com \
    --cc=kernelfans@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).