All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Samuel Ortiz <sortiz@dbear.engr.sgi.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] rmap 13a
Date: Tue, 7 May 2002 11:03:28 -0700	[thread overview]
Message-ID: <20020507180328.GS15756@holomorphy.com> (raw)
In-Reply-To: <20020507183741.A25245@infradead.org>

On Mon, May 06, 2002 at 11:17:26PM -0300, Rik van Riel wrote:
>> rmap 13a:
>>   - NUMA changes for page_address                         (Samuel Ortiz)

On Tue, May 07, 2002 at 06:37:41PM +0100, Christoph Hellwig wrote:
> I don't think the changes makes sense.  If calculating page_address is
> complicated and slow enough to place it out-of-lin using page->virtual
> is much better.

On Tue, May 07, 2002 at 06:37:41PM +0100, Christoph Hellwig wrote:
> I'd suggest backing this patch out and instead always maintain page->virtual
> for discontigmem.  While at this as a little cleanup you might want to
> define WANT_PAGE_VIRTUAL based on CONFIG_HIGHMEM || CONFIG_DISCONTIGMEM
> at the top of mm.h instead of cluttering it up.
> 	Christoph

This is a time/space tradeoff that may not necessarily be the case for
all discontiguous memory architectures. It seems to be so for SGI's
machines, though. I advocated this as a matter of generality, despite
not having a specific example of a machine that wants it. It's not
difficult to produce examples of small-memory architectures with
discontiguous memory, though SGI's discontigmem implementation does
not appear to be in widespread use for them.


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/

  reply	other threads:[~2002-05-07 18:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07  2:17 [PATCH] rmap 13a Rik van Riel
2002-05-07  2:17 ` Rik van Riel
2002-05-07 17:37 ` Christoph Hellwig
2002-05-07 18:03   ` William Lee Irwin III [this message]
2002-05-08 11:06   ` Samuel Ortiz
2002-05-08 11:13     ` William Lee Irwin III
2002-05-08 13:40     ` Rik van Riel
2002-05-08 18:21   ` Roman Zippel
2002-05-08 21:34     ` William Lee Irwin III
2002-05-08 22:34       ` Roman Zippel
2002-05-08 22:42         ` William Lee Irwin III
2002-05-08 22:50           ` William Lee Irwin III
2002-05-08 23:26           ` Roman Zippel
2002-05-09  1:29             ` William Lee Irwin III
2002-05-09 12:33               ` Roman Zippel
2002-05-09 14:09                 ` William Lee Irwin III
2002-05-09 15:36                   ` Roman Zippel
2002-05-09 17:42                     ` William Lee Irwin III
2002-05-09 21:45                       ` Roman Zippel
2002-05-09 23:13                         ` William Lee Irwin III
2002-05-10 11:37                           ` Roman Zippel
2002-05-10 16:28                             ` William Lee Irwin III
2002-05-10 19:48                               ` Roman Zippel
2002-05-08 21:50     ` 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=20020507180328.GS15756@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=sortiz@dbear.engr.sgi.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.