From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [Bug #14141] order 2 page allocation failures in iwlagn Date: Tue, 20 Oct 2009 06:57:57 +0900 Message-ID: <20091019215757.GC12570@think> References: <3onW63eFtRF.A.xXH.oMTxKB@chimera> <20091014103002.GA5027@csn.ul.ie> <200910141510.11059.elendil@planet.nl> <200910190133.33183.elendil@planet.nl> <20091019140151.GC9036@csn.ul.ie> <20091019161815.GA11487@think> <20091019170115.GA4593@infradead.org> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20091019170115.GA4593-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christoph Hellwig Cc: Mel Gorman , Frans Pop , David Rientjes , KOSAKI Motohiro , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Pekka Enberg , Reinette Chatre , Bartlomiej Zolnierkiewicz , Karol Lewandowski , Mohamed Abbas , Jens Axboe , "John W. Linville" , linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org On Mon, Oct 19, 2009 at 01:01:15PM -0400, Christoph Hellwig wrote: > On Tue, Oct 20, 2009 at 01:18:15AM +0900, Chris Mason wrote: > > Waiting doesn't make it synchronous from the elevator point of view ;) > > If you're using WB_SYNC_NONE, it's a async write. WB_SYNC_ALL makes it > > a sync write. I only see WB_SYNC_NONE in vmscan.c, so we should be > > using the async congestion wait. (the exception is xfs which always > > does async writes). > > That's only because those people who did the global sweep did not bother > to convert it or even tell the list about it. I have a patch in my > QA queue to change it.. Yes, we just didn't realize XFS was missed. Sorry. I wasn't trying to blame xfs for being behind, just mentioning that we've got about 10 different variables here and I'm having a hard time figuring out which ones to push on. -chris