Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758274Ab1ELRhU (ORCPT ); Thu, 12 May 2011 13:37:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5687 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758223Ab1ELRhT (ORCPT ); Thu, 12 May 2011 13:37:19 -0400 Date: Thu, 12 May 2011 19:36:28 +0200 From: Andrea Arcangeli To: David Rientjes 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 Subject: Re: [PATCH 3/3] mm: slub: Default slub_max_order to 0 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 Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1177 Lines: 24 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/