From: "Bulent Abali" <abali@us.ibm.com>
To: linux-mm@kvack.org
Subject: (struct page *)->list
Date: Sat, 7 Apr 2001 18:30:07 -0400 [thread overview]
Message-ID: <OFF7EEC8B0.74CE8D02-ON85256A27.0079C289@pok.ibm.com> (raw)
Question about the ->list field in linux/include/mm.h
typedef struct page
{
struct list_head list;
...
} mem_map_t;
I have a device driver that allocates pages with
alloc_pages(gfp_mask,0) call. I want to use
the ->list field and associated list_add() and list_del()
functions to keep track of my pages. The driver allocates
with GFP_KERNEL and GFP_HIGHUSER and will use the PAE
mode as well.
The question is if I unhook the page->list field after
page=alloc_page() and add page->list to my private linked list
will that cause a problem elsewhere in the kernel?
>From my reading the code, the list field
is used only when pages are in the free page pool or
in the mmap code in mm/filemap.c. Appreciate any suggestions.
Bulent
--
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:[~2001-04-07 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-07 22:30 Bulent Abali [this message]
2001-04-08 1:39 ` Benjamin C.R. LaHaise
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=OFF7EEC8B0.74CE8D02-ON85256A27.0079C289@pok.ibm.com \
--to=abali@us.ibm.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