All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Linus Torvalds <torvalds@transmeta.com>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Daniel Phillips <phillips@bonn-fries.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: VM in 2.4.7-pre hurts...
Date: 09 Jul 2001 10:25:25 +0200	[thread overview]
Message-ID: <m3wv5iik5m.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.33.0107090944120.305-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0107090944120.305-100000@mikeg.weiden.de>

Hi Mike,

On Mon, 9 Jul 2001, Mike Galbraith wrote:
> I don't know exactly what is happening, but I do know _who_ is
> causing the problem I'm seeing.. it's tmpfs.  When mounted on /tmp
> and running X/KDE, the tar [1] will oom my box every time because
> page_launder trys and always failing to get anything scrubbed after
> the tar has run for a while.  Unmount tmpfs/restart X and do the
> same tar, and all is well.
> 
> (it's not locked pages aparantly. I modified page_launder to move
> those to the active list, and refill_inactive_scan to rotate them to
> the end of the active list.  inactive_dirty list still grows ever
> larger, filling with 'stuff' that page_launder can't clean until
> you're totally oom)

Do you have set the size parameter for tmpfs? Else it will grow until
oom.

Another point I see with tmpfs is the following: tmpfs writepage
simply moves the page to the swap cache. But it does not schedule a
writeout of the page. So we have to scan the swap cache to really free
memory.

Greetings
		Christoph



  reply	other threads:[~2001-07-09  8:27 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0107081640570.308-100000@mikeg.weiden.de>
2001-07-08 15:43 ` VM in 2.4.7-pre hurts Rik van Riel
2001-07-08 17:15   ` Mike Galbraith
2001-07-08 17:58   ` Linus Torvalds
2001-07-08 18:23     ` Rik van Riel
2001-07-08 19:30       ` Linus Torvalds
2001-07-09  2:59         ` Linus Torvalds
2001-07-10  2:56           ` Andrea Arcangeli
2001-07-10  4:03             ` Linus Torvalds
2001-07-10  4:20               ` Linus Torvalds
2001-07-10  5:43                 ` Andrea Arcangeli
2001-07-10 14:56                   ` Andrea Arcangeli
2001-07-10 18:46                     ` Linus Torvalds
2001-07-10  5:11               ` Andrea Arcangeli
2001-07-09  7:56       ` Mike Galbraith
2001-07-09  8:25         ` Christoph Rohland [this message]
2001-07-09  9:18           ` Mike Galbraith
2001-07-09  9:29             ` Christoph Rohland
2001-07-09  9:38               ` Mike Galbraith
2001-07-09 11:17                 ` Mike Galbraith
2001-07-09 11:30                   ` Christoph Rohland
2001-07-09 12:26                     ` Mike Galbraith
2001-07-09 11:25                 ` Christoph Rohland
2001-07-09 12:20                   ` Mike Galbraith
2001-07-09 16:20                 ` Linus Torvalds
2001-07-09 19:44                   ` Christoph Rohland
2001-07-09 20:46                     ` Linus Torvalds
2001-07-11 19:39                       ` Christoph Rohland
2001-07-11  1:05                 ` Marcelo Tosatti
2001-07-11  4:03                   ` Mike Galbraith
2001-07-12  5:00       ` David Lang
     [not found] <Pine.LNX.4.33L.0107071542420.17825-100000@duckman.distro.conectiva>
2001-07-07 18:54 ` Linus Torvalds
2001-07-07 20:11   ` Rik van Riel
2001-07-08 17:11     ` Linus Torvalds
2001-07-08 18:29       ` Rik van Riel
2001-07-07 13:41 Jeff Garzik
2001-07-07 14:05 ` Jeff Garzik
2001-07-07 17:28 ` Linus Torvalds
2001-07-07 17:37   ` Jeff Garzik
2001-07-07 17:53     ` Linus Torvalds
2001-07-07 18:08       ` Jeff Garzik
2001-07-07 18:11         ` Rik van Riel
2001-07-07 21:33       ` Alan Cox
2001-07-07 18:00     ` Rik van Riel
2001-07-07 21:25   ` Alan Cox
2001-07-07 21:29     ` Rik van Riel
2001-07-07 21:34       ` Jeff Garzik
2001-07-07 21:43       ` Alan Cox
2001-07-07 21:45         ` Rik van Riel

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=m3wv5iik5m.fsf@linux.local \
    --to=cr@sap.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=phillips@bonn-fries.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.