[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200911042157.25020.elendil@planet.nl>
Date: Wed, 4 Nov 2009 21:57:21 +0100
From: Frans Pop <elendil@...net.nl>
To: Mel Gorman <mel@....ul.ie>
Cc: Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org,
linux-kernel@...r.kernel.org,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Jiri Kosina <jkosina@...e.cz>,
Sven Geggus <lists@...hsschwanzdomain.de>,
Karol Lewandowski <karol.k.lewandowski@...il.com>,
Tobias Oetiker <tobi@...iker.ch>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Rik van Riel <riel@...hat.com>,
Christoph Lameter <cl@...ux-foundation.org>,
Stephan von Krawczynski <skraw@...net.com>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [PATCH 3/3] vmscan: Force kswapd to take notice faster when high-order watermarks are being hit
On Wednesday 04 November 2009, Mel Gorman wrote:
> Agreed. I'll start from scratch again trying to reproduce what you're
> seeing locally. I'll try breaking my network card so that it's making
> high-order atomics and see where I get. Machines that were previously
> tied up are now free so I might have a better chance.
Hmmm. IMO you're looking at this from the wrong side. You don't need to
break your network card because the SKB problems are only the *result* of
the change, not the *cause*.
I can reproduce the desktop freeze just as easily when I'm using wired
(e1000e) networking and when I'm not streaming music at all, but just
loading that 3rd gitk instance.
So it's not
"I get a desktop freeze because of high order allocations from wireless
during swapping",
but
"during very heavy swapping on a system with an encrypted LMV volume
group containing (encrypted) fs and (encrytpted) swap, the swapping
gets into some semi-stalled state *causing* a long desktop freeze
and, if there also happens to be some process trying higher order
allocations, failures of those allocations".
I have tried to indicate this in the past, but it may have gotten lost in
the complexity of the issue.
An important clue is still IMO that during the first part of the freezes
there is very little disk activity for a long time. Why would that be when
the system is supposed to be swapping like hell?
Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists