From: "yunfeng zhang" <zyf.zeroos@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Zhou Yingchao" <yingchao.zhou@gmail.com>
Subject: Re: [PATCH 2.6.16.29 1/1] memory: enhance Linux swap subsystem
Date: Wed, 27 Dec 2006 11:33:39 +0800 [thread overview]
Message-ID: <4df04b840612261933g6eab036rb474930828dadb6d@mail.gmail.com> (raw)
In-Reply-To: <67029b170612260103o9193346hde726a3f09afa57f@mail.gmail.com>
To multiple address space, multiple memory inode architecture, we can introduce
a new core object -- section which has several features
1) Section is used as the atomic unit to contain the pages of a VMA residing in
the memory inode of the section.
2) When page migration occurs among different memory inodes, new secion should
be set up to trace the pages.
3) Section can be scanned by the SwapDaemon of its memory inode directely.
4) All sections of a VMA are excluded with each other not overlayed.
5) VMA is made up of sections totally, but its section objects scatter on memory
inodes.
So to the architecture, we can deploy swap subsystem on an
architecture-independent layer by section and scan pages batchly.
The idea issued by me is whether swap subsystem should be deployed on layer 2 or
layer 3 which is described in Documentation/vm_pps.txt of my patch. To multiple
memory inode architecture, the special memory model should be encapsulated on
layer 3 (architecture-dependent), I think.
next prev parent reply other threads:[~2006-12-27 3:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 8:18 yunfeng zhang
2006-12-26 9:03 ` Zhou Yingchao
2006-12-27 3:33 ` yunfeng zhang [this message]
2006-12-30 5:50 ` Zhou Yingchao
2007-01-05 7:35 ` yunfeng zhang
2007-01-05 7:45 ` yunfeng zhang
2006-12-27 3:38 ` yunfeng zhang
2006-12-27 18:44 ` Pavel Machek
2006-12-29 6:45 ` yunfeng zhang
2006-12-29 9:15 ` Pavel Machek
2006-12-29 15:50 ` Randy Dunlap
2007-01-05 23:10 zyf.zeroos
2007-01-09 8:27 ` yunfeng zhang
[not found] <200701092047.43248.a1426z@gawab.com>
2007-01-10 2:51 ` yunfeng zhang
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=4df04b840612261933g6eab036rb474930828dadb6d@mail.gmail.com \
--to=zyf.zeroos@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yingchao.zhou@gmail.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
all inboxes | Powered by JetHome®