From: Andrew Morton <akpm@osdl.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] get_user_pages shortcut for anonymous pages.
Date: Mon, 5 Apr 2004 14:29:40 -0700 [thread overview]
Message-ID: <20040405142940.5a4ed583.akpm@osdl.org> (raw)
In-Reply-To: <20040405142433.GA5955@mschwid3.boeblingen.de.ibm.com>
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
>
> > You'd need to teach follow_page() to return one of three values:
> > page-present, page-not-present-but-used-to-be or
> > page-not-present-and-never-was.
> Hmm, this would get ugly because follow_page calls
> follow_huge_addr and follow_huge_pmd for system with highmem. I
> really don't want to change follow_page. Instead I added a check
> for pgd_none/pgd_bad and pmd_none/pmd_bad for page directory
> entries needed for the pages in question. After all the patch is
> supposed to prevent the creation of page tables so why not check
> the pgd/pmd slots?
>
> diff -urN linux-2.6/mm/memory.c linux-2.6-bigcore/mm/memory.c
OK.. I'm not sure that this patch makes sense though. I mean, if your
test had gone and dirtied all these pages rather than forcing the coredump
code to do it, we'd still exhaust all physical memory with pagetables,
assuming you have enough swapspace. So I don't see we're gaining much?
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-04-05 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 14:24 Martin Schwidefsky
2004-04-05 21:29 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 7:24 Martin Schwidefsky
2004-04-02 14:17 Martin Schwidefsky
2004-04-05 5:59 ` Andrew Morton
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=20040405142940.5a4ed583.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox