From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id D106A6B005A for ; Wed, 15 Jul 2009 06:44:38 -0400 (EDT) From: Mel Gorman Subject: [PATCH 0/3] Suppress page allocator warnings about order >= MAX_ORDER (resend) Date: Wed, 15 Jul 2009 12:23:09 +0100 Message-Id: <1247656992-19846-1-git-send-email-mel@csn.ul.ie> Sender: owner-linux-mm@kvack.org To: Andrew Morton Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Linux Memory Management List , Heinz Diehl , David Miller , Arnaldo Carvalho de Melo , Mel Gorman List-ID: This is a resend of the series to suppress warnings when the order is too high but the caller knows how to handle it. The possible problematic patch in this series is patch 3 altering dccp. A better fix for that problem would be to use alloc_large_system_hash() and replace the code in question. A patch to do that could be buried in a git tree somewhere and the people cc'd should know if it exists and where. 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, 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/ . Don't email: email@kvack.org