linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "Manish Ahuja" <ahuja@austin.ibm.com>
Cc: mahuja@us.ibm.com, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] pseries: phyp dump: Variable size reserve space.
Date: Wed, 16 Apr 2008 15:22:42 -0500	[thread overview]
Message-ID: <3ae3aa420804161322i10e5efe2v2f74e1f9d6698e90@mail.gmail.com> (raw)
In-Reply-To: <47FAB221.7050406@austin.ibm.com>

On 07/04/2008, Manish Ahuja <ahuja@austin.ibm.com> wrote:
> A small proposed change in the amount of reserve space we allocate during boot.
>  Currently we reserve 256MB only.
>  The proposed change does one of the 3 things.
>
>  A. It checks to see if there is cmdline variable set and if found sets the
>    value to it. OR
>  B. It computes 5% of total ram and rounds it down to multiples of 256MB. AND
>  C. Compares the rounded down value and returns larger of two values, the new
>    computed value or 256MB.
>
>  Again this is for large systems who have excess memory.
>
[...]
>   early_param("phyp_dump", early_phyp_dump_enabled);

I'm pretty sure you will want to document this boot param in the documentation,
as well as add a few words about why it might be interesting to users (i.e.
that its for large systems...)

--linas

  parent reply	other threads:[~2008-04-16 20:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 23:45 [PATCH] pseries: phyp dump: Variable size reserve space Manish Ahuja
2008-04-08  2:43 ` Olof Johansson
2008-04-09 17:32   ` Manish Ahuja
2008-04-09 19:39     ` Segher Boessenkool
2008-04-10  1:36       ` Paul Mackerras
2008-04-10  3:10         ` Segher Boessenkool
2008-04-09 17:37   ` Manish Ahuja
2008-04-09 18:30     ` Olof Johansson
2008-04-09 18:43       ` Manish Ahuja
2008-04-09 18:59         ` Olof Johansson
2008-04-11 23:31 ` Manish Ahuja
2008-04-15  6:24   ` Paul Mackerras
2008-04-15 22:56     ` Manish Ahuja
2008-04-16 19:42       ` Joel Schopp
2008-04-16 20:22 ` Linas Vepstas [this message]
2008-04-18 19:08   ` Manish Ahuja

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=3ae3aa420804161322i10e5efe2v2f74e1f9d6698e90@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=ahuja@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahuja@us.ibm.com \
    --cc=paulus@samba.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).