From: Andrew Lutomirski <luto@mit.edu>
To: Mel Gorman <mgorman@suse.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Pádraig Brady" <P@draigbrady.com>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Colin King" <colin.king@canonical.com>,
"Minchan Kim" <minchan.kim@gmail.com>,
"Rik van Riel" <riel@redhat.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Stop kswapd consuming 100% CPU when highest zone is small
Date: Sat, 25 Jun 2011 08:23:37 -0600 [thread overview]
Message-ID: <BANLkTintLEcJvNzzspYRUV8fCx9=9dGDnA@mail.gmail.com> (raw)
In-Reply-To: <1308926697-22475-1-git-send-email-mgorman@suse.de>
On Fri, Jun 24, 2011 at 8:44 AM, Mel Gorman <mgorman@suse.de> wrote:
> (Built this time and passed a basic sniff-test.)
>
> During allocator-intensive workloads, kswapd will be woken frequently
> causing free memory to oscillate between the high and min watermark.
> This is expected behaviour. Unfortunately, if the highest zone is
> small, a problem occurs.
>
[...]
I've been running these for a couple days with no problems, although I
haven't been trying to reproduce the problem. (Well, no problems
related to memory management.)
I suspect that my pet unnecessary-OOM-kill bug is still around, but
that's probably not related, especially since I can trigger it if I
stick 8 GB of RAM in this laptop.
Thanks,
Andy
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-25 14:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 14:44 [PATCH 0/4] Stop kswapd consuming 100% CPU when highest zone is small Mel Gorman
2011-06-24 14:44 ` [PATCH 1/4] mm: vmscan: Correct check for kswapd sleeping in sleeping_prematurely Mel Gorman
2011-06-25 21:33 ` Rik van Riel
2011-06-27 6:10 ` Minchan Kim
2011-06-28 21:49 ` Andrew Morton
2011-06-29 10:57 ` Pádraig Brady
2011-06-30 9:39 ` Mel Gorman
2011-06-30 2:23 ` KOSAKI Motohiro
2011-06-24 14:44 ` [PATCH 2/4] mm: vmscan: Do not apply pressure to slab if we are not applying pressure to zone Mel Gorman
2011-06-25 21:40 ` Rik van Riel
2011-06-28 23:38 ` Minchan Kim
2011-06-30 2:37 ` KOSAKI Motohiro
2011-06-24 14:44 ` [PATCH 3/4] mm: vmscan: Evaluate the watermarks against the correct classzone Mel Gorman
2011-06-25 21:42 ` Rik van Riel
2011-06-27 6:53 ` Minchan Kim
2011-06-28 12:52 ` Mel Gorman
2011-06-28 23:23 ` Minchan Kim
2011-06-28 23:23 ` Minchan Kim
2011-06-24 14:44 ` [PATCH 4/4] mm: vmscan: Only read new_classzone_idx from pgdat when reclaiming successfully Mel Gorman
2011-06-25 23:17 ` Rik van Riel
2011-06-30 9:05 ` KOSAKI Motohiro
2011-06-30 10:19 ` Mel Gorman
2011-07-19 16:09 ` Minchan Kim
2011-07-20 10:48 ` Mel Gorman
2011-07-21 15:30 ` Minchan Kim
2011-07-21 16:07 ` Mel Gorman
2011-07-21 16:36 ` Minchan Kim
2011-07-21 17:01 ` Mel Gorman
2011-07-22 0:21 ` Minchan Kim
2011-07-22 7:42 ` Mel Gorman
2011-06-25 14:23 ` Andrew Lutomirski [this message]
2011-07-21 15:37 ` [PATCH 0/4] Stop kswapd consuming 100% CPU when highest zone is small Minchan Kim
2011-07-21 16:09 ` Mel Gorman
2011-07-21 16:24 ` Minchan Kim
2011-07-21 16:36 ` Andrew Lutomirski
2011-07-21 16:42 ` Minchan Kim
2011-07-21 16:58 ` Andrew Lutomirski
2011-07-22 0:30 ` Minchan Kim
2011-07-22 13:21 ` Andrew Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 13:43 Mel Gorman
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='BANLkTintLEcJvNzzspYRUV8fCx9=9dGDnA@mail.gmail.com' \
--to=luto@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=P@draigbrady.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).