From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Robert Love <rml@tech9.net>,
Linus Torvalds <torvalds@transmeta.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 16:09:46 -0700 [thread overview]
Message-ID: <20020720230946.GH1096@holomorphy.com> (raw)
In-Reply-To: <244469929.1027180137@[10.10.2.3]>
At some point in the past, Robert Love wrote:
>> 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.
On Sat, Jul 20, 2002 at 03:48:59PM -0700, Martin J. Bligh wrote:
> 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 ;-))
I won't stand in the way of any of this, the list.h sort-of suggestion
was merely part of questioning the pgdat_next change. In fact, it was
meant more to point out what you just did, that the iterator takes the
field out of direct usage except for a couple of places.
I'll stand behind these changes as they are now.
Cheers,
Bill
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Robert Love <rml@tech9.net>,
Linus Torvalds <torvalds@transmeta.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 16:09:46 -0700 [thread overview]
Message-ID: <20020720230946.GH1096@holomorphy.com> (raw)
In-Reply-To: <244469929.1027180137@[10.10.2.3]>
At some point in the past, Robert Love wrote:
>> 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.
On Sat, Jul 20, 2002 at 03:48:59PM -0700, Martin J. Bligh wrote:
> 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 ;-))
I won't stand in the way of any of this, the list.h sort-of suggestion
was merely part of questioning the pgdat_next change. In fact, it was
meant more to point out what you just did, that the iterator takes the
field out of direct usage except for a couple of places.
I'll stand behind these changes as they are now.
Cheers,
Bill
--
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 23:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 20:22 [PATCH] for_each_pgdat Robert Love
2002-07-20 20:22 ` Robert Love
2002-07-20 20:43 ` Martin J. Bligh
2002-07-20 20:43 ` Martin J. Bligh
2002-07-20 20:54 ` William Lee Irwin III
2002-07-20 20:54 ` William Lee Irwin III
2002-07-20 21:00 ` Linus Torvalds
2002-07-20 21:00 ` Linus Torvalds
2002-07-20 21:37 ` Robert Love
2002-07-20 21:37 ` Robert Love
2002-07-20 22:48 ` Martin J. Bligh
2002-07-20 22:48 ` Martin J. Bligh
2002-07-20 23:09 ` William Lee Irwin III [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=20020720230946.GH1096@holomorphy.com \
--to=wli@holomorphy.com \
--cc=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 \
/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.