From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755587Ab2K0Vue (ORCPT ); Tue, 27 Nov 2012 16:50:34 -0500 Received: from zene.cmpxchg.org ([85.214.230.12]:35229 "EHLO zene.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753345Ab2K0Vud (ORCPT ); Tue, 27 Nov 2012 16:50:33 -0500 Date: Tue, 27 Nov 2012 16:49:28 -0500 From: Johannes Weiner To: Rik van Riel Cc: Linus Torvalds , Andrew Morton , Mel Gorman , George Spelvin , Johannes Hirte , Tomas Racek , Jan Kara , Dave Hansen , Josh Boyer , Valdis Kletnieks , Jiri Slaby , Thorsten Leemhuis , Zdenek Kabelac , Bruno Wolff III , linux-mm , Linux Kernel Mailing List Subject: Re: kswapd craziness in 3.7 Message-ID: <20121127214928.GA20253@cmpxchg.org> References: <1354049315-12874-1-git-send-email-hannes@cmpxchg.org> <50B52DC4.5000109@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50B52DC4.5000109@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 27, 2012 at 04:16:52PM -0500, Rik van Riel wrote: > On 11/27/2012 03:58 PM, Linus Torvalds wrote: > >Note that in the meantime, I've also applied (through Andrew) the > >patch that reverts commit c654345924f7 (see commit 82b212f40059 > >'Revert "mm: remove __GFP_NO_KSWAPD"'). > > > >I wonder if that revert may be bogus, and a result of this same issue. > >Maybe that revert should be reverted, and replaced with your patch? > > > >Mel? Zdenek? What's the status here? > > Mel posted several patches to fix the kswapd issue. This one is > slightly more risky than the outright revert, but probably preferred > from a performance point of view: > > https://lkml.org/lkml/2012/11/12/151 > > It works by skipping the kswapd wakeup for THP allocations, only > if compaction is deferred or contended. Just to clarify, this would be a replacement strictly for the __GFP_NO_KSWAPD removal revert, to control how often kswapd is woken up for higher order allocations like THP. My patch is to fix how kswapd actually does higher order reclaim, and it is required either way. [ But isn't the _reason_ why the "wake up kswapd more carefully for THP" patch was written kind of moot now since it was developed against a crazy kswapd? It would certainly need to be re-evaluated. My (limited) testing didn't show any issues anymore with waking kswapd unconditionally once it's fixed. ]