linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@nl.linux.org>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: Christoph Rohland <hans-christoph.rohland@sap.com>,
	MM mailing list <linux-mm@kvack.org>,
	woodman@missioncriticallinux.com,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [Patch] shm cleanups
Date: Thu, 4 Nov 1999 20:02:55 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.10.9911042000300.647-100000@imladris.dummy.home> (raw)
In-Reply-To: <Pine.LNX.4.10.9911041851010.5467-100000@chiara.csoma.elte.hu>

On Thu, 4 Nov 1999, Ingo Molnar wrote:
> On 4 Nov 1999, Christoph Rohland wrote:
> 
> > I do get swapping also with 8GB of RAM, but it runs out of memory
> > before running out of swap space since prepare_highmem_swapout is
> > failing way to often.
> 
> ho humm. I think prepare_highmem_swapout() has a design bug. It's way too
> naive in low memory situations, it should keep a short list of pages for
> emergency swapout. It's the GFP_ATOMIC that is failing too often, right?
> 
> i believe we should have some explicit mechanizm that tells vmscan that
> there is 'IO in progress which will result in more memory', to distinct
> between true out-of-memory and 'wait a little bit to get more RAM' cases?

I think I see what is going on here. Kswapd sees that memory is
low an "frees" a bunch of high memory pages, causing those pages
to be shifted to low memory so the total number of free pages
stays just as low as when kswapd started.

This can result in in-memory swap storms, we should probably
limit the number of in-transit async himem pages to 256 or some
other even smaller number.

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  reply	other threads:[~1999-11-04 19:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-03 21:30 Christoph Rohland
1999-11-04  8:10 ` Ingo Molnar
1999-11-04 12:40   ` Christoph Rohland
1999-11-04 17:58     ` Ingo Molnar
1999-11-04 19:02       ` Rik van Riel [this message]
1999-11-04 22:30         ` Ingo Molnar
1999-11-05  0:14           ` Andrea Arcangeli
1999-11-05 12:35             ` Christoph Rohland
1999-11-05 13:18               ` Andrea Arcangeli
1999-11-05 16:16                 ` Christoph Rohland
1999-11-05 16:21                   ` Andrea Arcangeli
1999-11-05 16:28                     ` Christoph Rohland
1999-11-05 10:36           ` Christoph Rohland
  -- strict thread matches above, loose matches on Subject: below --
1999-11-03 19:17 Christoph Rohland

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=Pine.LNX.4.10.9911042000300.647-100000@imladris.dummy.home \
    --to=riel@nl.linux.org \
    --cc=hans-christoph.rohland@sap.com \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=torvalds@transmeta.com \
    --cc=woodman@missioncriticallinux.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