From: Hirokazu Takahashi <taka@valinux.co.jp>
To: iwamoto@valinux.co.jp
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com, pavel@suse.cz
Subject: Re: memory hotremove prototype, take 3
Date: Tue, 02 Dec 2003 15:43:19 +0900 (JST) [thread overview]
Message-ID: <20031202.154319.84357522.taka@valinux.co.jp> (raw)
In-Reply-To: <20031202030109.3A01B7007A@sv1.valinux.co.jp>
Hello,
> > > During hotunplug, you copy pages to new locaion. Would it simplify
> > > code if you forced them to be swapped out, instead? [Yep, it would be
> > > slower...]
> >
> > There are some pages that will have to be copied (e.g. pages that
> > the user "mlock()d" should still be locked in their new location,
> > same for hugetlbfs pages).
And some pages which aren't associated with backing store like sysfs or
ramdisk have to be, too.
> Using kswapd is easy, but doesn't always work well. The patch
> contains the code to ignore page accessed bits when kswapd is run on
> disabled zones, but that's not enough for swapping out frequently used
> pages.
> In my patch, page copying, or "remapping", solves this problem by
> blocking accesses to the page under operation.
Thank you,
Hirokazu Takahashi.
next prev parent reply other threads:[~2003-12-02 6:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 20:12 memory hotremove prototype, take 3 Luck, Tony
2003-12-02 3:01 ` IWAMOTO Toshihiro
2003-12-02 6:43 ` Hirokazu Takahashi [this message]
2003-12-02 22:26 ` Yasunori Goto
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 0:45 Luck, Tony
2003-12-03 17:57 Luck, Tony
2003-12-03 5:19 Perez-Gonzalez, Inaky
2003-12-01 3:41 IWAMOTO Toshihiro
2003-12-01 19:56 ` Pavel Machek
2003-12-03 19:41 ` Martin J. Bligh
2003-12-04 3:58 ` IWAMOTO Toshihiro
2003-12-04 5:38 ` Martin J. Bligh
2003-12-04 15:44 ` IWAMOTO Toshihiro
2003-12-04 17:12 ` Martin J. Bligh
2003-12-04 18:27 ` Jesse Barnes
2003-12-04 18:29 ` Martin J. Bligh
2003-12-04 18:59 ` Jesse Barnes
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=20031202.154319.84357522.taka@valinux.co.jp \
--to=taka@valinux.co.jp \
--cc=iwamoto@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).