From: Manish Ahuja <ahuja@austin.ibm.com>
To: Olof Johansson <olof@lixom.net>
Cc: mahuja@us.ibm.com, linuxppc-dev@ozlabs.org,
linasvepstas@gmail.com, paulus@samba.org
Subject: Re: [PATCH] pseries: phyp dump: Variable size reserve space.
Date: Wed, 09 Apr 2008 12:32:20 -0500 [thread overview]
Message-ID: <47FCFDA4.10709@austin.ibm.com> (raw)
In-Reply-To: <20080408024352.GA32761@lixom.net>
Olof Johansson wrote:
> These make for some really long variable names and lines. I know from
> experience, since I've picked unneccessary long driver names in the past
> myself. :)
>
> How about just naming the new variables reserve_bootvar, etc? The name
> of the struct they're in makes it obvious what they're for.
>
Yeah, I guess thats a good suggestion. Will truncate it.
>
>> +static inline unsigned long phyp_dump_calculate_reserve_size(void)
>> +{
>> + unsigned long tmp;
>> +
>> + if (phyp_dump_info->phyp_dump_reserve_bootvar)
>> + return phyp_dump_info->phyp_dump_reserve_bootvar;
>> +
>> + /* divide by 20 to get 5% of value */
>> + tmp = lmb_end_of_DRAM();
>> + do_div(tmp, 20);
>> +
>> + /* round it down in multiples of 256 */
>> + tmp = tmp & ~0x000000001FFFFFFF;
>
> That's 512MB, isn't it?
>
No, its 5 % of memory and then rounded down to 256 MB multiples.
so if you 4GB its 256MB.
if you have 8 GB its 512 MB etc.
>
> -Olof
next prev parent reply other threads:[~2008-04-09 17:32 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 [this message]
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
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=47FCFDA4.10709@austin.ibm.com \
--to=ahuja@austin.ibm.com \
--cc=linasvepstas@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahuja@us.ibm.com \
--cc=olof@lixom.net \
--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 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.