linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Shaohua Li" <shaoh.li@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Cc: hch@infradead.org
Subject: swap out memory
Date: Mon, 6 Aug 2007 20:53:20 +0800	[thread overview]
Message-ID: <288dbef70708060553i4405f8d9lefa6132c86190d7b@mail.gmail.com> (raw)

Hi,
I'm trying to swap out kvm guest pages. The idea is to free some pages
when memory pressure is high. kvm has special things to handle like
shadow page tables. Before guest page is released, we need free some
data, that is guest page has 'private' data, so we can't directly make
the guest page swapout with Linux swapout mechanism. I'd like write
guest pages to a file or swap. kvm guest pages are in its address
space and added into lru list like normal page (the address space is
very like a shmem file's, kvm has a memory based file system). When
vmscan decided to free one guest page, kvm guest pages's
aops.writepage will free the private data and then write it out to
block device. The problem is how to write guest pages. I thought we
have some choices:

1. swap it to swapfile. Like shmem does, using move_to_swap_cache to
move guest page from its address space to swap address space, and
finally it's written to swapfile. This method works well, but as kvm
is a module, I must export some swap relelated APIs, which Christoph
Hellwig dislike.

2. write it to a file. Just like the stack fs does, in kvm address
space's .writepage, let low fs's aops write the page. This involves
allocating a new page for low fs file and copy kvm page to the new
page. As this (doing swap) is done when memory is tight, allocating
new page isn't good. The copy isn't good too.

3.write it to a file. Using bmap to get file's block info and using
low level sumbit_bio for read/write. This is like what swapfile does,
but we do it by ourselves, so don't need use swap symbols.

Do you have any suggestion which method is good, or if you have better
choice I could try?

Thanks,
Shaohua

--
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:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2007-08-06 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 12:53 Shaohua Li [this message]
2007-08-08 12:03 ` Shaohua Li

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=288dbef70708060553i4405f8d9lefa6132c86190d7b@mail.gmail.com \
    --to=shaoh.li@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@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