mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "yunfeng zhang" <zyf.zeroos@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Improvement on memory subsystem
Date: Wed, 23 Aug 2006 18:39:14 +0800	[thread overview]
Message-ID: <4df04b840608230339q1e0f3ce3y846dc40c0cf40299@mail.gmail.com> (raw)
In-Reply-To: <4df04b840607180303i3d8c8bd0o4d2a24752ec2e150@mail.gmail.com>

New design has been appended into my OS, it's mainly focused on how to
allocate swap pages for each PrivateVMA efficiently in swap daemon.

Let's first see the PTE array snapshot of a PrivateVMA,
           U-U-P-P-P-S-S
U: UnmappedPTE; P: PTE; S: SwappedPTE.

The snapshot shows that the pages of the PrivateVMA has an
access-affinity. The 3rd, 4th and 5th have been accessed since last
scanning on the PrivateVMA, other PTEs aren't still touched.

A concept is introduced here to describe the accessed PTEs -- series.
So we've got three series (1st and 2nd), (3rd, 4th and 5th) and (6th
and 7th) from the snapshot.

The design is allocating swap pages by series. It should be more
efficient for future page-fault to page-in them.

Further discussion in my new documentation
http://www.cublog.cn/u/21764/upfile/060823181124.zip.  In section
"Memory Daemons >> SwapDaemon and PrivateVMA" and "Class Repository >>
SwapDaemon". There's also sample code in Implementation subdirectory
of the archives.

      parent reply	other threads:[~2006-08-23 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 10:03 yunfeng zhang
2006-07-18 12:18 ` Valdis.Kletnieks
2006-07-19  3:44   ` yunfeng zhang
2006-07-19  9:18   ` Ian Stirling
2006-07-19 14:56     ` Valdis.Kletnieks
2006-07-18 16:25 ` Pekka Enberg
2006-07-19  3:21   ` yunfeng zhang
2006-07-19  8:30     ` Pekka Enberg
2006-07-19 10:13       ` yunfeng zhang
2006-07-19 10:35         ` Pekka Enberg
2006-07-24  9:01 ` yunfeng zhang
2006-07-24 14:55   ` David Lang
2006-07-25  8:33     ` yunfeng zhang
2006-08-23 10:39 ` yunfeng zhang [this message]

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=4df04b840608230339q1e0f3ce3y846dc40c0cf40299@mail.gmail.com \
    --to=zyf.zeroos@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®