From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Robert Love <rml@tech9.net>, Linus Torvalds <torvalds@transmeta.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
akpm@zip.com.au, riel@conectiva.com.br,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] for_each_pgdat
Date: Sat, 20 Jul 2002 15:48:59 -0700 [thread overview]
Message-ID: <244469929.1027180137@[10.10.2.3]> (raw)
In-Reply-To: <1027201039.1085.812.camel@sinai>
>> Ok guys, you three (and whoever else wants to play? ;) fight it out amonst
>> yourselves, I'll wait for the end result (iow: I'll just ignore both
>> patches for now).
>
> No no... the issues are fairly orthogonal.
>
> Attached is a patch with the for_each_pgdat implementation and
> s/node_next/pgdat_next/ per Martin.
I'm happy with this (obviously ;-))
> If Bill wants to convert pgdats to lists that is fine but is another
> step. Let's get in this first batch and that can be done off this.
As we now reference them in only two places (the macro defn and
numa.c:_alloc_pages) it hardly seems worth converting to lists ... ?
(I'm going to take an axe to NUMA _alloc_pages in a minute anyway ;-))
M.
--
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/
next prev parent reply other threads:[~2002-07-20 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 20:22 Robert Love
2002-07-20 20:43 ` Martin J. Bligh
2002-07-20 20:54 ` William Lee Irwin III
2002-07-20 21:00 ` Linus Torvalds
2002-07-20 21:37 ` Robert Love
2002-07-20 22:48 ` Martin J. Bligh [this message]
2002-07-20 23:09 ` William Lee Irwin III
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='244469929.1027180137@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.com \
/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