Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754713AbaDRUsv (ORCPT ); Fri, 18 Apr 2014 16:48:51 -0400 Received: from Mycroft.westnet.com ([216.187.52.7]:42920 "EHLO mycroft.westnet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754022AbaDRUss (ORCPT ); Fri, 18 Apr 2014 16:48:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <21329.36761.970643.523119@quad.stoffel.home> Date: Fri, 18 Apr 2014 16:48:25 -0400 From: "John Stoffel" To: Andrew Morton Cc: Mel Gorman , Robert Haas , Josh Berkus , Andres Freund , Christoph Lameter , Linux-MM , LKML , Michal Hocko Subject: Re: [PATCH 0/2] Disable zone_reclaim_mode by default v2 In-Reply-To: <20140418130543.8619064c0e5d26cd914c4c3c@linux-foundation.org> References: <1396945380-18592-1-git-send-email-mgorman@suse.de> <20140418130543.8619064c0e5d26cd914c4c3c@linux-foundation.org> X-Mailer: VM 8.2.0b under 23.2.1 (x86_64-pc-linux-gnu) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "Andrew" == Andrew Morton writes: Andrew> On Tue, 8 Apr 2014 09:22:58 +0100 Mel Gorman wrote: >> Changelog since v1 >> o topology comment updates >> >> When it was introduced, zone_reclaim_mode made sense as NUMA distances >> punished and workloads were generally partitioned to fit into a NUMA >> node. NUMA machines are now common but few of the workloads are NUMA-aware >> and it's routine to see major performance due to zone_reclaim_mode being >> enabled but relatively few can identify the problem. This is unclear here. "see major performance due" doesn't make sense to me. -- 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/