Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758478AbZFVPoc (ORCPT ); Mon, 22 Jun 2009 11:44:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758215AbZFVPnk (ORCPT ); Mon, 22 Jun 2009 11:43:40 -0400 Received: from gir.skynet.ie ([193.1.99.77]:35164 "EHLO gir.skynet.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757372AbZFVPng (ORCPT ); Mon, 22 Jun 2009 11:43:36 -0400 From: Mel Gorman To: Andrew Morton Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Linux Memory Management List , Heinz Diehl , Mel Gorman Subject: [PATCH 0/3] Suppress page allocator warnings about order >= MAX_ORDER Date: Mon, 22 Jun 2009 16:43:31 +0100 Message-Id: <1245685414-8979-1-git-send-email-mel@csn.ul.ie> X-Mailer: git-send-email 1.5.6.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1002 Lines: 21 The page allocator warns once when callers specify an order that is too high. This is because the path is slow and it's important to verify that callers are really doing the right thing and recovering by specifying smaller orders rather than simply falling back to vmalloc(). The problem is that there is no way of suppressing the warning when the callers are doing the right thing. Patch 1 of this series allows the warning to be suppressed with __GFP_NOWARN. The second two patches suppress warnings generated by the profile= and the DCCP network protocol as those callers are recovering in a sensible fashion. kernel/profile.c | 5 +++-- mm/page_alloc.c | 4 +++- net/dccp/proto.c | 4 ++-- 3 files changed, 8 insertions(+), 5 deletions(-) -- 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/