From: Andrew Lutomirski <luto@mit.edu>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Minchan Kim <minchan.kim@gmail.com>,
mgorman@suse.de, KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
aarcange@redhat.com, kamezawa.hiroyu@jp.fujitsu.com,
fengguang.wu@intel.com, andi@firstfloor.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, riel@redhat.com
Subject: Re: Easy portable testcase! (Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux))
Date: Tue, 14 Jun 2011 08:32:48 -0400 [thread overview]
Message-ID: <BANLkTimJVvGaEZBm1+tRvkNYoCv4p0rk7Q@mail.gmail.com> (raw)
In-Reply-To: <20110614101047.GG6371@cmpxchg.org>
On Tue, Jun 14, 2011 at 6:10 AM, Johannes Weiner <hannes@cmpxchg.org> wrote:
> On Sun, May 29, 2011 at 08:28:46PM -0400, Andrew Lutomirski wrote:
>> On Sun, May 29, 2011 at 2:28 PM, Minchan Kim <minchan.kim@gmail.com> wrote:
>> >>
>> >> It works only if the zone meets high watermark. If allocation is
>> >> faster than reclaim(ie, it's true for slow swap device), the zone
>> >> would remain congested.
>> >> It means swapout would block.
>> >> As we see the OOM log, we can know that DMA32 zone can't meet high watermark.
>> >>
>> >> Does my guessing make sense?
>> >
>> > Hi Andrew.
>> > I got failed your scenario in my machine so could you be willing to
>> > test this patch for proving my above scenario?
>> > The patch is just revert patch of 0e093d99[do not sleep on the
>> > congestion queue...] for 2.6.38.6.
>> > I would like to test it for proving my above zone congestion scenario.
>> >
>> > I did it based on 2.6.38.6 for your easy apply so you must apply it
>> > cleanly on vanilla v2.6.38.6.
>> > And you have to add !pgdat_balanced and shrink_slab patch.
>>
>> No, because my laptop just decided that it doesn't like to turn on. :(
>>
>> I'll test it on my VM on Tuesday and (fingers crossed) on my repaired
>> laptop next weekend.
>
> Any updates on this?
>
Sorry, got distracted by writing my thesis.
This patch (Revert "writeback: do not sleep on the congestion queue if
there are no congested BDIs or if significant congestion is not being
encountered in the current zone") does not fix the problem; if
anything it triggers more easily with the patch (at least in KVM).
--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>
prev parent reply other threads:[~2011-06-14 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 20:17 Easy portable testcase! (Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux)) Andrew Lutomirski
2011-05-26 8:18 ` KOSAKI Motohiro
2011-05-26 23:58 ` Minchan Kim
2011-05-29 18:28 ` Minchan Kim
2011-05-30 0:28 ` Andrew Lutomirski
2011-06-14 10:10 ` Johannes Weiner
2011-06-14 12:32 ` Andrew Lutomirski [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=BANLkTimJVvGaEZBm1+tRvkNYoCv4p0rk7Q@mail.gmail.com \
--to=luto@mit.edu \
--cc=aarcange@redhat.com \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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).