From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] more discontig fun
Date: Wed, 30 Jul 2003 17:17:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105958545513688@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105942849830042@msgid-missing>
On Tue, Jul 29, 2003 at 03:43:58PM -0700, David Mosberger wrote:
> Hi Jesse,
>
> Two quick comments:
>
> +
> + /* for discontig machines, we do this in discontig.c */
> if (smp_processor_id() = 0) {
> cpu_data = __alloc_bootmem(PERCPU_PAGE_SIZE * NR_CPUS, PERCPU_PAGE_SIZE,
>
> This comment seems out of place. Isn't it trying to say that all of
> per_cpu_init() is done in discontig.c for NUMA? If so the comment
> should be in front of the #ifdef around CONFIG_DISCONTIGMEM. Also,
> I'm wondering whether we shouldn't split off the contig-mem case into
> a separate file. I don't like those #ifdef CONFIG_DISCONTIGMEM. It
> would be better to control that via the Makefile.
A quick grep shows quite a few #ifndef CONFIG_DISCONTIGMEMs, I'll see if
I can clean some stuff up and put it into contig.c.
> On to this one:
>
> +struct memmap_count_callback_data {
> + int node;
> + unsigned long num_physpages;
> + unsigned long num_dma_physpages;
> + unsigned long min_pfn;
> + unsigned long max_pfn;
> +} cdata;
>
> I don't like non-reentrant code. Can't you allocate the variable on
> the stack and pass a pointer to it via the callback interface? Yes,
> we may not be needing re-entrancy right now, but I just think it's bad
> design to have non-reentrant code (unless there are good reasons for
> it).
Ok, I'll fix this too. Thanks for looking at it.
Jesse
next prev parent reply other threads:[~2003-07-30 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 21:35 [PATCH] more discontig fun Jesse Barnes
2003-07-30 17:17 ` Jesse Barnes [this message]
2003-07-30 23:32 ` Jesse Barnes
2003-07-30 23:53 ` Keith Owens
2003-07-30 23:56 ` Jesse Barnes
2003-07-31 0:32 ` David Mosberger
2003-07-31 20:28 ` Jesse Barnes
2003-08-04 23:27 ` David Mosberger
2003-08-04 23:30 ` Jesse Barnes
2003-09-08 18:31 ` Jesse Barnes
2003-09-08 18:41 ` Jesse Barnes
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=marc-linux-ia64-105958545513688@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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