linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gleb Natapov <gleb@redhat.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	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 11:54:42 +0000	[thread overview]
Message-ID: <20100119115442.131efa78@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100119075205.GI14345@redhat.com>

> 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
> guest much large then host memory, but I want system to swap out only
> guest's memory.

So this isn't an API question this is an obscure corner case testing
question.

> 
> > 
> > It would be probably useful if you could point us to the application
> > source code that actually wants this feature.
> > 
> This is two line patch to qemu that calls mlockall(MCL_CURRENT|MCL_FUTURE)
> at the beginning of the main() and changes guest memory allocation to
> use MAP_UNLOCKED flag. All alternative solutions in this thread suggest
> that I should rewrite qemu + all library it uses. You see why I can't
> take them seriously?

And you want millions of users to have kernels with weird extra functions
whole sole value is one test environment you wish to run

See why we can't take you seriously either ?

--
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>

  parent reply	other threads:[~2010-01-19 11:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 13:37 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 [this message]
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

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=20100119115442.131efa78@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.c.morrow@gmail.com \
    --cc=gleb@redhat.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=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