From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Cc: rmk@arm.linux.org.uk, nico@cam.org, davem@redhat.com,
davidm@hpl.hp.com, alan@lxorguk.ukuu.org.uk
Subject: pte_pagenr/MAP_NR deleted in pre6
Date: Thu, 10 Aug 2000 10:18:49 -0700 (PDT) [thread overview]
Message-ID: <200008101718.KAA33467@google.engr.sgi.com> (raw)
Thought I would send out a quick note about a change I put into test6.
Basically, to make it easier to implement DISCONTIGMEM systems, the
concepts of page/mem_map number/index has been killed from the generic
(non architecture specific) parts of the kernel. This includes MAP_NR,
pte_pagenr and max_mapnr (although max_mapnr is used by a lot of
architectures, it is not used by the generic kernel anymore).
New macros that have been born to replace the above ones are
virt_to_page (thusly named by Linus!), which will take a kernel direct
mapped address as input and provide the corresponding struct page. The
other one is VALID_PAGE(), which given a page struct, determines whether
it is a valid page struct and represents _physical_ memory.
Both of virt_to_page and VALID_PAGE are in include/asm*/page.h. I have
tried to make sure there were no mistakes when making the changes for
the various architectures, but I am sure I goofed up a few cases, so
apologies in advance.
Also, as I have suggested before, the pte_page implementation in
sparc/sparc64 should be cleaned up, and the usages of MAP_NR in the
arm code. Russell, Linus has not put in the final patch that will
allow DISCONTIGMEM systems to lay out their mem_map arrays however
they see fit, I have resent it to him, if that is put in, we can get
down to simplifying most of the DISCONTIG arch code.
Thanks.
Kanoj
--
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.eu.org/Linux-MM/
next reply other threads:[~2000-08-10 17:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 17:18 Kanoj Sarcar [this message]
2000-08-11 2:24 ` David S. Miller
2000-08-14 0:34 ` Anton Blanchard
2000-08-11 11:50 ` Roman Zippel
2000-08-11 13:20 ` Russell King
2000-08-11 14:56 ` Roman Zippel
2000-08-12 9:18 ` Bjorn Wesen
2000-08-11 17:21 ` Kanoj Sarcar
2000-08-14 9:29 ` Roman Zippel
2000-08-15 16:19 ` Stephen C. Tweedie
2000-08-16 8:25 ` Roman Zippel
2000-08-16 17:13 ` Kanoj Sarcar
2000-08-16 18:20 ` Stephen C. Tweedie
2000-08-16 18:24 ` David S. Miller
2000-08-16 19:53 ` Stephen C. Tweedie
2000-08-16 18:47 ` Kanoj Sarcar
2000-08-16 18:39 ` David S. Miller
2000-08-16 19:30 ` Stephen C. Tweedie
2000-08-16 22:22 ` Kanoj Sarcar
2000-08-17 9:11 ` Stephen C. Tweedie
2000-08-17 19:07 ` Kanoj Sarcar
2000-08-17 19:01 ` David S. Miller
2000-08-17 19:19 ` Alan Cox
2000-08-17 19:20 ` David S. Miller
2000-08-17 19:33 ` Alan Cox
2000-08-17 19:36 ` Kanoj Sarcar
2000-09-07 14:31 ` Ralf Baechle
2000-08-17 19:50 ` Kanoj Sarcar
2000-08-17 19:41 ` David S. Miller
2000-09-07 14:26 ` Ralf Baechle
2000-08-17 19:56 ` Alan Cox
2000-08-17 19:24 ` Alan Cox
2000-08-17 19:32 ` Kanoj Sarcar
2000-08-17 19:30 ` David S. Miller
2000-08-17 20:00 ` Kanoj Sarcar
2000-08-16 18:17 ` Stephen C. Tweedie
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=200008101718.KAA33467@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=nico@cam.org \
--cc=rmk@arm.linux.org.uk \
/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