From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ben LaHaise <bcrl@redhat.com>,
Daniel Phillips <phillips@bonn-fries.net>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: [RFC][DATA] re "ongoing vm suckage"
Date: Tue, 7 Aug 2001 23:25:17 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0108072320530.12561-100000@freak.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.31.0108070932400.31167-100000@cesium.transmeta.com>
On Tue, 7 Aug 2001, Linus Torvalds wrote:
> On Tue, 7 Aug 2001, Linus Torvalds wrote:
> >
> > Sorry, I should have warned people: pre5 is a test-release that was
> > intended solely for Leonard Zubkoff who has been helping with trying to
> > debug a FS livelock condition.
>
> In case people are interested, the livelock _seems_ to be rather simple:
> when we run out of immediately available memory in "refill_freelist()", we
> seem to do all the wrong things.
>
> This condition doesn't happen under normal load, because under normal load
> most allocators are of the regular "GFP_USER" kind. But it looks like
> under certain loads you get into the situation that the system isn't doing
> much else than just doing alloc_pages(GFP_NOFS), and that one seems to be
> giving up really easily.
>
> Apparently so easily, in fact, that kswapd doesn't even bother to try to
> make things better. I _know_ that it doesn't show up as
> "inactive_shortage()", because the machine has tons of inactive_dirty
> pages (buffers), and I suspect that "free_shortage()" also decides that we
> have enough pages.
>
> So I _think_ that what happens is:
> - alloc_pages() itself isn't making any progress, because it's called
> with GFP_NOFS and thus cannot touch a lot of the pages.
> - we wake up kswapd to try to help, but kswapd doesn't do anything
> because it thinks things are fine.
If the reason for this problem is really what you're thinking, the
following together with the total_free_shortage() patch should fix the
problem.
(please apply this on the stock tree. Even if it does not fix the problem
we're seeing now, it is correct)
--- mm/page_alloc.c.origf Wed Aug 8 00:45:51 2001
+++ mm/page_alloc.c Wed Aug 8 00:46:19 2001
@@ -453,7 +453,7 @@
if (gfp_mask & __GFP_WAIT) {
if (!order || total_free_shortage()) {
int progress = try_to_free_pages(gfp_mask);
- if (progress || (gfp_mask & __GFP_FS))
+ if (progress || (gfp_mask & __GFP_IO))
goto try_again;
/*
* Fail in case no progress was made and the
--
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/
prev parent reply other threads:[~2001-08-08 2:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 23:44 Ben LaHaise
2001-08-04 1:29 ` Rik van Riel
2001-08-04 3:06 ` Daniel Phillips
2001-08-04 3:13 ` Linus Torvalds
2001-08-04 3:23 ` Rik van Riel
2001-08-04 3:35 ` Linus Torvalds
2001-08-04 3:26 ` Ben LaHaise
2001-08-04 3:34 ` Rik van Riel
2001-08-04 3:38 ` Linus Torvalds
2001-08-04 3:48 ` Linus Torvalds
2001-08-04 4:14 ` Ben LaHaise
2001-08-04 4:20 ` Linus Torvalds
2001-08-04 4:39 ` Ben LaHaise
2001-08-04 4:47 ` Linus Torvalds
2001-08-04 5:13 ` Ben LaHaise
2001-08-04 5:28 ` Linus Torvalds
2001-08-04 6:37 ` Linus Torvalds
2001-08-04 5:38 ` Marcelo Tosatti
2001-08-04 7:13 ` Rik van Riel
2001-08-04 23:28 ` [PATCH] Unlazy activate (was: re "ongoing vm suckage") Daniel Phillips
2001-08-04 14:22 ` [RFC][DATA] re "ongoing vm suckage" Mike Black
2001-08-04 17:08 ` Linus Torvalds
2001-08-04 20:54 ` Jonathan Morton
2001-08-05 4:19 ` Michael Rothwell
2001-08-05 18:40 ` Marcelo Tosatti
2001-08-05 20:20 ` Linus Torvalds
2001-08-06 20:32 ` Rob Landley
2001-08-05 15:24 ` Mike Black
2001-08-05 20:04 ` Linus Torvalds
2001-08-05 20:23 ` Alan Cox
2001-08-05 20:33 ` Linus Torvalds
2001-08-04 16:21 ` Mark Hemment
2001-08-07 15:45 ` Ben LaHaise
2001-08-07 16:22 ` Linus Torvalds
2001-08-07 16:51 ` Ben LaHaise
2001-08-07 17:08 ` Linus Torvalds
2001-08-07 18:17 ` Andrew Morton
2001-08-07 18:40 ` Ben LaHaise
2001-08-07 21:33 ` Daniel Phillips
2001-08-07 21:33 ` Linus Torvalds
2001-08-07 17:04 ` Linus Torvalds
2001-08-07 17:11 ` Rik van Riel
2001-08-07 19:12 ` Linus Torvalds
2001-08-07 19:21 ` Rik van Riel
2001-08-07 20:50 ` Linus Torvalds
2001-08-07 23:36 ` Linus Torvalds
2001-08-07 17:26 ` Chris Mason
2001-08-07 18:13 ` Daniel Phillips
2001-08-07 18:40 ` Chris Mason
2001-08-07 19:52 ` Linus Torvalds
2001-08-07 20:22 ` Chris Mason
2001-08-08 1:08 ` Theodore Tso
2001-08-08 1:13 ` Linus Torvalds
2001-08-08 2:25 ` Marcelo Tosatti [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=Pine.LNX.4.21.0108072320530.12561-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox