From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162136AbbKEQRp (ORCPT ); Thu, 5 Nov 2015 11:17:45 -0500 Received: from mail-wm0-f52.google.com ([74.125.82.52]:34450 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1033218AbbKEQQO (ORCPT ); Thu, 5 Nov 2015 11:16:14 -0500 From: mhocko@kernel.org To: Cc: Andrew Morton , LKML Subject: [PATCH 0/3] __GFP_REPEAT cleanup Date: Thu, 5 Nov 2015 17:15:57 +0100 Message-Id: <1446740160-29094-1-git-send-email-mhocko@kernel.org> X-Mailer: git-send-email 2.6.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, while working on something unrelated I've checked the current usage of __GFP_REPEAT in the tree. It seems that a good half of it is and always has been bogus because __GFP_REPEAT has always been about high order allocations while we are using it for order-0 or very small orders very often. It seems that a big pile of them is just a copy&paste when a code has been adopted from one arch to another. I think it makes some sense to get rid of them because they are just making the semantic more unclear. The series is based on linux-next tree and $ git grep __GFP_REPEAT next/master | wc -l 106 and with the patch $ git grep __GFP_REPEAT | wc -l 44 There are probably more users which do not need the flag but I have focused on the trivially superfluous ones here.