linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Manish Ahuja <ahuja@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: mahuja@us.ibm.com, linuxppc-dev@ozlabs.org, linasvepstas@gmail.com
Subject: Re: [PATCH] pseries: phyp dump: Variable size reserve space.
Date: Tue, 15 Apr 2008 17:56:14 -0500	[thread overview]
Message-ID: <4805328E.2050709@austin.ibm.com> (raw)
In-Reply-To: <18436.18955.450131.623072@cargo.ozlabs.ibm.com>

Paul,

The aim is to have more flex space for the kernel on machines with more resources. Although the dump will be collected pretty fast and the memory released really early on allowing the machine to have the full memory available, this alleviates any issues that can be caused by having way too little memory on very very large systems during those few minutes.

-Manish



Paul Mackerras wrote:
> Manish Ahuja writes:
> 
>> B. It computers 5% of total ram and rounds it down to multiples of 256MB.
>> C. Compares the rounded down value and returns larger of 256MB or the new
>>    computed value.
> 
> So if we have 10GB of memory or more we'll use reserve more than
> 256MB.  What is the advantage of reserving more than 256MB of memory?
> 
> Paul.

  reply	other threads:[~2008-04-15 22:56 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 [this message]
2008-04-16 19:42       ` Joel Schopp
2008-04-16 20:22 ` Linas Vepstas
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=4805328E.2050709@austin.ibm.com \
    --to=ahuja@austin.ibm.com \
    --cc=linasvepstas@gmail.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).