From: Andrea Arcangeli Subject: Re: [PATCH 3/3] mm: slub: Default slub_max_order to 0 Date: Thu, 12 May 2011 19:36:28 +0200 Message-ID: <20110512173628.GJ11579@random.random> References: <1305127773-10570-1-git-send-email-mgorman@suse.de> <1305127773-10570-4-git-send-email-mgorman@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mel Gorman , Andrew Morton , James Bottomley , Colin King , Raghavendra D Prabhu , Jan Kara , Chris Mason , Christoph Lameter , Pekka Enberg , Rik van Riel , Johannes Weiner , linux-fsdevel , linux-mm , linux-kernel , linux-ext4 To: David Rientjes Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-Id: linux-ext4.vger.kernel.org On Wed, May 11, 2011 at 01:38:47PM -0700, David Rientjes wrote: > kswapd and doing compaction for the higher order allocs before falling Note that patch 2 disabled compaction by clearing __GFP_WAIT. What you describe here would be patch 2 without the ~__GFP_WAIT addition (so keeping only ~GFP_NOFAIL). Not clearing __GFP_WAIT when compaction is enabled is possible and shouldn't result in bad behavior (if compaction is not enabled with current SLUB it's hard to imagine how it could perform decently if there's fragmentation). You should try to benchmark to see if it's worth it on the large NUMA systems with heavy network traffic (for normal systems I doubt compaction is worth it but I'm not against trying to keep it enabled just in case). On a side note, this reminds me to rebuild with slub_max_order in .bss on my cellphone (where I can't switch to SLAB because of some silly rfs vfat-on-steroids proprietary module). -- 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: email@kvack.org