mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rick Haines <rick@kuroyi.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	Andrea Arcangeli <andrea@suse.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.10 VM: what avoids from having lots of unwriteable inactive pages
Date: Tue, 25 Sep 2001 17:20:16 -0400	[thread overview]
Message-ID: <20010925172016.B860@sasami.kuroyi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0109250849480.7353-100000@penguin.transmeta.com> <Pine.LNX.4.33L.0109251311340.26091-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109251311340.26091-100000@duckman.distro.conectiva>

On Tue, Sep 25, 2001 at 01:13:37PM -0300, Rik van Riel wrote:
> On Tue, 25 Sep 2001, Linus Torvalds wrote:
> > On Tue, 25 Sep 2001, Rik van Riel wrote:
> > > >
> > > > swap_out() will deactivate everything it finds to be not-recently used,
> > > > and that's how the inactive list ends up getting replenished.
> > >
> > > mlock()
> >
> > Hey, if you've mlock'ed more than your available memory, there's nothing
> > the VM layer can do. Except maybe a nice printk("Kiss your *ss goodbye");

Shouldn't there be a threshold where mlock will fail?
Or are you saying that in general mlocking lots of memory will screw the
VM?

> But if you've mlock()ed enough to clog up the inactive
> list, the VM could just move the pages it cannot free
> back to the active list and it will come across those
> pages which are freeable eventually.
> 
> Note that the maximum amount of mlock()ed memory is way
> higher than the maximum amount of pages the system puts
> on the inactive list.
> 
> (at least, it was last I looked at the maximum number
> of mlocked pages)
> 
> regards,
> 
> Rik
> --
> IA64: a worthy successor to the i860.
> 
> 		http://www.surriel.com/
> http://www.conectiva.com/	http://distro.conectiva.com/
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Rick (rick@kuroyi.net)
http://dxr3.sourceforge.net

I think the slogan of the fansubbers puts
it best: "Cheaper than crack, and lots more fun."

  reply	other threads:[~2001-09-25 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 22:27 Marcelo Tosatti
2001-09-24 23:54 ` Linus Torvalds
2001-09-24 22:39   ` Marcelo Tosatti
2001-09-25  1:20     ` Linus Torvalds
2001-09-25 15:04       ` Rik van Riel
2001-09-25 15:50         ` Linus Torvalds
2001-09-25 16:13           ` Rik van Riel
2001-09-25 21:20             ` Rick Haines [this message]
2001-09-25 20:01               ` Marcelo Tosatti

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=20010925172016.B860@sasami.kuroyi.net \
    --to=rick@kuroyi.net \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=riel@conectiva.com.br \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®