From: Hirokazu Takahashi <taka@valinux.co.jp>
To: ashwin_s_rao@yahoo.com
Cc: Valdis.Kletnieks@vt.edu, haveblue@us.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Atomic operation for physically moving a page (for memory defragmentation)
Date: Wed, 23 Jun 2004 19:32:34 +0900 (JST) [thread overview]
Message-ID: <20040623.193234.60195426.taka@valinux.co.jp> (raw)
In-Reply-To: <20040619031536.61508.qmail@web10902.mail.yahoo.com>
Hi,
> > > I want to copy a page from one physical location
> > to
> > > another (taking the appr. locks).
> >
> > At the risk of sounding stupid, what problem are you
> > trying to solve by copying
> > a page? Not only (as you note) could the page be
> > referenced by multiple
> > processes, it could (conceivably) belong to a kernel
> > slab or something, or be a
> > buffer for an in-flight I/O request, or any number
> > of other possibly-racy
> > situations.
>
> The problem is the memory fragmentation. The code i am
> writing is for the memory defragmentation as proposed
> by Daniel Phillips, my project partner Alok mooley has
> given mailed a simple prototype in the mid of feb.
If you only care about anonymous memory, how do you think
about expanding the COW mechanism?
1. make all pages COW in a process space.
2. force to cause COW fault on the each page.
3. copy from the page to a new allocated page, and discard the old page.
You may preallocate new pages.
Thank you,
Hirokazu Takahashi.
--
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 10:32 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
2004-06-24 7:19 ` IWAMOTO Toshihiro
2004-06-24 11:31 ` Dave Hansen
2004-06-23 10:32 ` Hirokazu Takahashi [this message]
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=20040623.193234.60195426.taka@valinux.co.jp \
--to=taka@valinux.co.jp \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ashwin_s_rao@yahoo.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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