From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Richard Jerrell <jerrell@missioncriticallinux.com>
Cc: Szabolcs Szakacsits <szaka@f-secure.com>, linux-mm@kvack.org
Subject: Re: [PATCH] Reclaim orphaned swap pages
Date: Mon, 2 Apr 2001 21:19:33 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0104022114110.6947-100000@freak.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.21.0104021430160.12558-100000@jerrell.lowell.mclinux.com>
On Mon, 2 Apr 2001, Richard Jerrell wrote:
> > Actually if vm_enough_memory fails that prevents oom, apps get ENOMEM
> > instead of killed by oom_kill later. Moreover vm_enough_memory is long
> > different and apparently it's just overestimating free pages that makes
> > people unhappy with the resulted higher oom_kill/ENOMEM rate. If you
>
> That's not really what I'm getting at. Currently if you run a memory
> intensive application, quit after it's pages are on an lru, and try to
> restart, you won't be able to get the memory. This is because pages which
> are sitting around in the swap cache are not counted as free, and they
> should be, because they are freeable.
No. Dirty swapcache pages which have pte's referencing them are not
freeable.
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-03 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 18:17 Szabolcs Szakacsits
2001-04-02 18:40 ` Richard Jerrell
2001-04-02 18:40 ` Szabolcs Szakacsits
2001-04-03 0:19 ` Marcelo Tosatti [this message]
2001-04-03 13:27 ` Richard Jerrell
2001-04-03 22:11 ` Marcelo Tosatti
2001-04-04 14:29 ` Richard Jerrell
-- strict thread matches above, loose matches on Subject: below --
2001-04-02 15:17 Richard Jerrell
2001-03-31 22:46 Bulent Abali
2001-03-28 22:59 Stephen Tweedie
2001-03-30 19:59 ` Patrick O'Rourke
2001-03-30 22:16 ` Rik van Riel
2001-04-04 21:59 ` Stephen Tweedie
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.21.0104022114110.6947-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=jerrell@missioncriticallinux.com \
--cc=linux-mm@kvack.org \
--cc=szaka@f-secure.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