From: Gleb Natapov <gleb@redhat.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
akpm@linux-foundation.org, andrew.c.morrow@gmail.com,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH v6] add MAP_UNLOCKED mmap flag
Date: Tue, 19 Jan 2010 16:14:36 +0200 [thread overview]
Message-ID: <20100119141436.GA5238@redhat.com> (raw)
In-Reply-To: <1263910043.2163.24.camel@barrios-desktop>
On Tue, Jan 19, 2010 at 11:07:23PM +0900, Minchan Kim wrote:
> On Tue, 2010-01-19 at 09:52 +0200, Gleb Natapov wrote:
>
> > In my case (virtualization) I want to test/profile guest under heavy swapping
> > of a guests memory, so I intentionally create memory shortage by creating
>
> You mean "guest memory" that is area emulated DRAM in qemu?
> It is anonymous vma.
>
> > guest much large then host memory, but I want system to swap out only
> > guest's memory.
>
> Couldn't you use MADV_SEQUENTIAL on only guest memory area?
> It doesn't make side effect about readahead since it's anon area.
> And it would make do best effort to swap out guest's memory.
>
I can try, should be better then nothing I guess. Doesn't guaranty that
emulator memory will not be swapped out though.
--
Gleb.
--
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:[~2010-01-19 14:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:37 [PATCH v6] add MAP_UNLOCKED mmap flag Gleb Natapov
2010-01-18 14:09 ` Pekka Enberg
2010-01-18 14:19 ` Gleb Natapov
2010-01-18 14:32 ` Alan Cox
2010-01-18 14:35 ` Gleb Natapov
2010-01-18 14:49 ` Peter Zijlstra
2010-01-18 15:01 ` Gleb Natapov
2010-01-18 15:06 ` Peter Zijlstra
2010-01-18 15:11 ` Avi Kivity
2010-01-18 15:14 ` Peter Zijlstra
2010-01-18 15:19 ` Avi Kivity
2010-01-18 15:24 ` Peter Zijlstra
2010-01-18 15:41 ` Alan Cox
2010-01-18 15:44 ` Peter Zijlstra
2010-01-18 17:11 ` Gleb Natapov
2010-01-18 15:14 ` Gleb Natapov
2010-01-19 0:12 ` KOSAKI Motohiro
2010-01-18 16:05 ` Pekka Enberg
2010-01-18 17:08 ` Gleb Natapov
2010-01-18 18:09 ` Pekka Enberg
2010-01-18 18:19 ` Gleb Natapov
2010-01-18 19:10 ` Alan Cox
2010-01-19 7:17 ` Gleb Natapov
2010-01-19 7:37 ` Pekka Enberg
2010-01-19 7:52 ` Gleb Natapov
2010-01-19 8:07 ` Pekka Enberg
2010-01-19 8:26 ` Gleb Natapov
2010-01-19 8:44 ` Pekka Enberg
2010-01-19 10:40 ` Gleb Natapov
2010-01-19 12:48 ` Minchan Kim
2010-01-19 13:18 ` Pekka Enberg
2010-01-19 13:26 ` Gleb Natapov
2010-01-20 0:24 ` KOSAKI Motohiro
2010-01-19 11:54 ` Alan Cox
2010-01-19 12:07 ` Gleb Natapov
2010-01-19 13:21 ` Alan Cox
2010-01-19 14:07 ` Minchan Kim
2010-01-19 14:14 ` Gleb Natapov [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=20100119141436.GA5238@redhat.com \
--to=gleb@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.c.morrow@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
/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).