From: Dave Hansen <haveblue@us.ibm.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: ashwin_s_rao@yahoo.com, Valdis.Kletnieks@vt.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Atomic operation for physically moving a page (for memory defragmentation)
Date: Wed, 23 Jun 2004 13:56:30 -0700 [thread overview]
Message-ID: <1088024190.28102.24.camel@nighthawk> (raw)
In-Reply-To: <20040623.205906.71913783.taka@valinux.co.jp>
On Wed, 2004-06-23 at 04:59, Hirokazu Takahashi wrote:
> We should know that many part of kernel code will access the page
> without holding a lock_page(). The lock_page() can't block them.
No, but it will block them from establishing a new PTE to the page. You
need to:
1. make sure no new PTEs can be established to the page
2. make sure there are no valid PTEs to the page.
3. do the move
My suggestion relates to 1, only.
-- Dave
--
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-06-23 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 0:37 Atomic operation for physically moving a page Ashwin Rao
2004-06-19 1:03 ` Valdis.Kletnieks
2004-06-19 2:53 ` Dave Hansen
2004-06-19 3:15 ` Atomic operation for physically moving a page (for memory defragmentation) Ashwin Rao
2004-06-19 3:34 ` Valdis.Kletnieks
2004-06-19 4:25 ` Dave Hansen
2004-06-23 9:04 ` IWAMOTO Toshihiro
2004-06-23 11:59 ` Hirokazu Takahashi
2004-06-23 20:56 ` Dave Hansen [this message]
2004-06-24 7:19 ` IWAMOTO Toshihiro
2004-06-24 11:31 ` Dave Hansen
2004-06-23 10:32 ` Hirokazu Takahashi
2004-06-19 2:43 ` Atomic operation for physically moving a page Dave Hansen
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=1088024190.28102.24.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ashwin_s_rao@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
/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