linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	torvalds@linux-foundation.org, roland@kernel.org,
	kosaki.motohiro@gmail.com, penberg@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-rdma@vger.kernel.org,
	Mike Marciniszyn <infinipath@intel.com>
Subject: Re: [PATCH] mm: Revert pinned_vm braindamage
Date: Thu, 20 Jun 2013 13:34:31 +0200	[thread overview]
Message-ID: <20130620113431.GA12125@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306171417450.4234@ionos.tec.linutronix.de>


* Thomas Gleixner <tglx@linutronix.de> wrote:

> On Thu, 13 Jun 2013, Andrew Morton wrote:
> > Let's try to get this wrapped up?
> > 
> > On Thu, 6 Jun 2013 14:43:51 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> > 
> > > 
> > > Patch bc3e53f682 ("mm: distinguish between mlocked and pinned pages")
> > > broke RLIMIT_MEMLOCK.
> > 
> > I rather like what bc3e53f682 did, actually.  RLIMIT_MEMLOCK limits the
> > amount of memory you can mlock().  Nice and simple.
> > 
> > This pinning thing which infiniband/perf are doing is conceptually
> > different and if we care at all, perhaps we should be looking at adding
> > RLIMIT_PINNED.
> 
> Actually PINNED is just a stronger version of MEMLOCK. PINNED and 
> MEMLOCK are both preventing the page from being paged out. PINNED adds 
> the constraint of preventing minor faults as well.
> 
> So I think the really important tuning knob is the limitation of pages 
> which cannot be paged out. And this is what RLIMIT_MEMLOCK is about.
> 
> Now if you want to add RLIMIT_PINNED as well, then it only limits the 
> number of pages which cannot create minor faults, but that does not 
> affect the limitation of total pages which cannot be paged out.

Agreed.

( Furthermore, the RLIMIT_MEMLOCK semantics change actively broke code so
  this is not academic and it would be nice to progress with it. )

Thanks,

	Ingo

--
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:[~2013-06-20 11:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 12:43 Peter Zijlstra
2013-06-06 18:46 ` Christoph Lameter
2013-06-07 11:03   ` Peter Zijlstra
2013-06-07 14:52     ` Christoph Lameter
2013-06-17 11:08       ` Peter Zijlstra
2013-06-17 18:36         ` Christoph Lameter
2013-06-20 11:49           ` Ingo Molnar
2013-06-20 14:48             ` Christoph Lameter
2013-06-21  6:25               ` Roland Dreier
2013-06-21 14:44                 ` Christoph Lameter
2013-06-13 21:06 ` Andrew Morton
2013-06-17  9:45   ` Peter Zijlstra
2013-06-17 12:28   ` Thomas Gleixner
2013-06-20 11:34     ` Ingo Molnar [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=20130620113431.GA12125@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=infinipath@intel.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=roland@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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