linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: PG_DMA
Date: Mon, 13 Dec 1999 16:05:24 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.9912131603110.835-100000@penguin.transmeta.com> (raw)
In-Reply-To: <199912140001.QAA07712@google.engr.sgi.com>


On Mon, 13 Dec 1999, Kanoj Sarcar wrote:
>
> In 2.3.32-pre, I see that the PageDMA(page) macro has been changed to
> 
> #define PageDMA(page)            (contig_page_data.node_zones + ZONE_DMA == (page)->zone)
> 
> Why was this done? I would still prefer to see the PG_DMA bit, because
> for discontig platforms, there is not a "contig_page_data". In short, 
> this will break any platform that does use the CONFIG_DISCONTIGMEM code.

Actually, the REAL reason this was done is that PageDMA should just go
away completely.

If you grep for where it is actually used, you'll see that it's only used
in the page freeing code to see if this is a page we're interested in
freeing. And that needs to be eithe rremoved or revamped anyway - whether
it's going to be per-zone or global or whatever, the current test is just
noth worth it (what KIND of DMA? Is it the 20-bit ISA DMA or the 31-bit
broken PCI dma or the 32-bit real PCI dma or what?)

The DMA'ness of the page should be encoded as just the kind of zone it is
part of.

		Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

      reply	other threads:[~1999-12-14  0:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-14  0:01 PG_DMA Kanoj Sarcar
1999-12-14  0:05 ` Linus Torvalds [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=Pine.LNX.4.10.9912131603110.835-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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