From: Dave Hansen <haveblue@us.ibm.com>
To: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
Cc: Alok Mooley <rangdi@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Active Memory Defragmentation: Our implementation & problems
Date: 03 Feb 2004 23:10:52 -0800 [thread overview]
Message-ID: <1075878652.14155.416.camel@nighthawk> (raw)
In-Reply-To: <20040204065717.EFB277049E@sv1.valinux.co.jp>
On Tue, 2004-02-03 at 22:57, IWAMOTO Toshihiro wrote:
> At 03 Feb 2004 21:54:34 -0800,
> Dave Hansen wrote:
> > Moving file-backed pages is mostly handled already. You can do a
> > regular page-cache lookup with find_get_page(), make your copy,
> > invalidate the old one, then readd the new one. The invalidation can be
> > done in the same style as shrink_list().
>
> Actually, it is a bit more complicated.
> I have implemented similar functionality for memory hotremoval.
>
> See my post about memory hotremoval
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107354781130941&w=2
> for details.
> remap_onepage() and remapd() in the patch are the main functions.
remap_onepage() is quite a function. 300 lines. It sure does cover a
lot of ground. :)
Defragmentation is a bit easier than removal because it isn't as
mandatory. Instead of having to worry about waiting on things like
writeback, the defrag code can just bail.
--dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
Cc: Alok Mooley <rangdi@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Active Memory Defragmentation: Our implementation & problems
Date: 03 Feb 2004 23:10:52 -0800 [thread overview]
Message-ID: <1075878652.14155.416.camel@nighthawk> (raw)
In-Reply-To: <20040204065717.EFB277049E@sv1.valinux.co.jp>
On Tue, 2004-02-03 at 22:57, IWAMOTO Toshihiro wrote:
> At 03 Feb 2004 21:54:34 -0800,
> Dave Hansen wrote:
> > Moving file-backed pages is mostly handled already. You can do a
> > regular page-cache lookup with find_get_page(), make your copy,
> > invalidate the old one, then readd the new one. The invalidation can be
> > done in the same style as shrink_list().
>
> Actually, it is a bit more complicated.
> I have implemented similar functionality for memory hotremoval.
>
> See my post about memory hotremoval
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107354781130941&w=2
> for details.
> remap_onepage() and remapd() in the patch are the main functions.
remap_onepage() is quite a function. 300 lines. It sure does cover a
lot of ground. :)
Defragmentation is a bit easier than removal because it isn't as
mandatory. Instead of having to worry about waiting on things like
writeback, the defrag code can just bail.
--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-02-04 7:11 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 4:46 Active Memory Defragmentation: Our implementation & problems Alok Mooley
2004-02-03 4:46 ` Alok Mooley
2004-02-03 21:26 ` Dave Hansen
2004-02-03 21:26 ` Dave Hansen
2004-02-03 22:26 ` Martin J. Bligh
2004-02-03 22:26 ` Martin J. Bligh
2004-02-04 5:09 ` Alok Mooley
2004-02-04 5:09 ` Alok Mooley
2004-02-04 5:24 ` Mike Fedyk
2004-02-04 5:24 ` Mike Fedyk
2004-02-04 5:54 ` Dave Hansen
2004-02-04 5:54 ` Dave Hansen
2004-02-04 6:05 ` Martin J. Bligh
2004-02-04 6:05 ` Martin J. Bligh
2004-02-04 6:22 ` Dave Hansen
2004-02-04 6:22 ` Dave Hansen
2004-02-04 6:29 ` Martin J. Bligh
2004-02-04 6:29 ` Martin J. Bligh
2004-02-04 6:40 ` Dave Hansen
2004-02-04 6:40 ` Dave Hansen
2004-02-04 7:17 ` Martin J. Bligh
2004-02-04 7:17 ` Martin J. Bligh
2004-02-04 8:30 ` Andrew Morton
2004-02-04 8:30 ` Andrew Morton
2004-02-04 6:53 ` Doubt about statm_pgd_range patch Arunkumar
2004-02-04 6:57 ` Active Memory Defragmentation: Our implementation & problems IWAMOTO Toshihiro
2004-02-04 6:57 ` IWAMOTO Toshihiro
2004-02-04 7:10 ` Dave Hansen [this message]
2004-02-04 7:10 ` Dave Hansen
2004-02-04 7:50 ` IWAMOTO Toshihiro
2004-02-04 7:50 ` IWAMOTO Toshihiro
2004-02-04 10:33 ` Hirokazu Takahashi
2004-02-04 10:33 ` Hirokazu Takahashi
2004-02-04 18:33 ` Alok Mooley
2004-02-04 18:46 ` Dave Hansen
2004-02-04 18:54 ` Alok Mooley
2004-02-04 18:54 ` Alok Mooley
2004-02-04 19:07 ` Richard B. Johnson
2004-02-04 19:07 ` Richard B. Johnson
2004-02-04 19:18 ` Alok Mooley
2004-02-04 19:18 ` Alok Mooley
2004-02-04 19:33 ` Richard B. Johnson
2004-02-04 19:33 ` Richard B. Johnson
2004-02-05 5:07 ` Alok Mooley
2004-02-05 5:07 ` Alok Mooley
2004-02-05 19:03 ` Pavel Machek
2004-02-05 19:03 ` Pavel Machek
2004-02-04 19:35 ` Dave McCracken
2004-02-04 19:35 ` Dave McCracken
2004-02-04 21:59 ` Timothy Miller
2004-02-04 21:59 ` Timothy Miller
2004-02-04 23:24 ` Dave Hansen
2004-02-04 23:24 ` Dave Hansen
2004-02-05 16:32 ` Dave McCracken
2004-02-05 16:32 ` Dave McCracken
2004-02-04 19:37 ` Timothy Miller
2004-02-04 19:37 ` Timothy Miller
2004-02-04 19:43 ` Dave Hansen
2004-02-04 19:43 ` Dave Hansen
2004-02-04 19:59 ` Richard B. Johnson
2004-02-04 19:59 ` Richard B. Johnson
2004-02-04 19:56 ` Dave Hansen
2004-02-04 19:56 ` Dave Hansen
2004-02-05 5:19 ` Alok Mooley
2004-02-05 5:19 ` Alok Mooley
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 20:12 Mark_H_Johnson
2004-02-04 20:12 ` Mark_H_Johnson
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=1075878652.14155.416.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=iwamoto@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=rangdi@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.