From: Timur Tabi <ttabi@interactivesi.com>
To: Linux MM mailing list <linux-mm@kvack.org>
Subject: get_page_map in 2.2 vs 2.4
Date: Fri, 30 Jun 2000 12:38:19 -0500 [thread overview]
Message-ID: <20000630175015Z131177-21002+72@kanga.kvack.org> (raw)
In 2.2, the function get_page_map is this:
/*
* Given a physical address, is there a useful struct page pointing to it?
*/
static struct page * get_page_map(unsigned long page)
{
struct page *map;
if (MAP_NR(page) >= max_mapnr)
return 0;
if (page == ZERO_PAGE(page))
return 0;
map = mem_map + MAP_NR(page);
if (PageReserved(map))
return 0;
return map;
}
In 2.4, it's been changed to this:
/*
* Given a physical address, is there a useful struct page pointing to
* it? This may become more complex in the future if we start dealing
* with IO-aperture pages in kiobufs.
*/
static inline struct page * get_page_map(struct page *page)
{
if (page > (mem_map + max_mapnr))
return 0;
return page;
}
It appears that although the comment is no longer correct. In 2.2, the
function took an unsigned long and returned a pointer to a mem_map_t. In 2.4,
it takes a mem_map_t and returns it. This is hardly useful.
Am I missing something? What was wrong with the original implementation? And
why hasn't the comment changed?
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please don't cc: me, because then I'll just get two copies of the same message.
--
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-06-30 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-30 17:38 Timur Tabi [this message]
2000-07-03 13:59 ` 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=20000630175015Z131177-21002+72@kanga.kvack.org \
--to=ttabi@interactivesi.com \
--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