From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: William Chan <williamchan@google.com>
Cc: Hugh Dickins <hugh@veritas.com>, linux-mm@kvack.org, wchan212@gmail.com
Subject: Re: Swap Memory
Date: Fri, 6 Feb 2009 09:36:27 +0900 [thread overview]
Message-ID: <20090206093627.a90f23b5.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <77e5ae570902051240l1c7de8d5jbef5cfe55c156b6c@mail.gmail.com>
On Thu, 5 Feb 2009 12:40:31 -0800
William Chan <williamchan@google.com> wrote:
> > That could be changed, yes: but would multiply the amount of memory
> > needed for recording pages out of swap. The present design is to
> > minimize the memory needed by what's out on swap.
>
> Hopefully there will be less pages in swap than in system memory. If
> this is true - the overhead introduced should be minimal relative to
> the overhead the kernel already has for manging system memory pages.
>
In my experience, you can't assume that ;)
BTW, if you want to do that, changing device layer is much easier than changing
memory management layer.
Maybe adding device mapper for good-scheduled-swap(but not Raid0) is enough.
Preparing device-mapper layer which does
1. It can tie several devices of different size.
2. It chases each block's usage by some logic (LRU) and do block migration
if necessary.
3. priority between devices can be set by dm's user-land tools.
Hmm? But I'm not sure this is worth tring.
Thanks,
-Kame
--
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>
prev parent reply other threads:[~2009-02-06 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 20:38 William Chan
2009-02-05 18:33 ` Hugh Dickins
2009-02-05 19:10 ` William Chan
2009-02-05 19:57 ` Hugh Dickins
2009-02-05 20:40 ` William Chan
2009-02-06 0:36 ` KAMEZAWA Hiroyuki [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=20090206093627.a90f23b5.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=wchan212@gmail.com \
--cc=williamchan@google.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