From: Magnus Damm <magnus.damm@gmail.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Magnus Damm <magnus@valinux.co.jp>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] i386: nid_zone_sizes_init() update
Date: Thu, 6 Oct 2005 19:38:33 +0900 [thread overview]
Message-ID: <aec7e5c30510060338o7865119bu995e31dfb4bd54ee@mail.gmail.com> (raw)
In-Reply-To: <1128528774.26009.12.camel@localhost>
On 10/6/05, Dave Hansen <haveblue@us.ibm.com> wrote:
> On Wed, 2005-10-05 at 17:35 +0900, Magnus Damm wrote:
> > Broken out nid_zone_sizes_init() change from i386 NUMA emulation code.
> ...
> > -static inline unsigned long nid_size_pages(int nid)
> > -{
> > - return node_end_pfn[nid] - node_start_pfn[nid];
> > -}
> > -static inline int nid_starts_in_highmem(int nid)
> > -{
> > - return node_start_pfn[nid] >= max_low_pfn;
> > -}
>
> Hey, I liked those helpers!
Well, too bad for you! ;)
> When I suggested that you make your patches apply on top of the existing
> -mhp stuff, I didn't just mean that they should _apply_, they should
> probably mesh a little bit better. For instance, it would be very
> helpful to use those 'static inlines', or make a couple new ones if you
> need them.
Okey, I think I understand. And I agree that more effort could be put
into this to make the code look better. I thought this change was
required for the NUMA emulation code, but it turns out it wasn't. I
guess keeping the code as is and ignoring the patch is probably the
best solution.
Thanks!
/ magnus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2005-10-06 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 8:35 Magnus Damm
2005-10-05 15:10 ` Martin J. Bligh
2005-10-05 16:25 ` Dave Hansen
2005-10-05 16:12 ` Dave Hansen
2005-10-06 10:38 ` Magnus Damm [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=aec7e5c30510060338o7865119bu995e31dfb4bd54ee@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=magnus@valinux.co.jp \
/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