From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751075AbdEaQE2 (ORCPT ); Wed, 31 May 2017 12:04:28 -0400 Received: from mx2.suse.de ([195.135.220.15]:52598 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750898AbdEaQE1 (ORCPT ); Wed, 31 May 2017 12:04:27 -0400 Date: Wed, 31 May 2017 18:04:23 +0200 From: Michal Hocko To: Tom Lendacky Cc: linux-mm@kvack.org, LKML Subject: strange PAGE_ALLOC_COSTLY_ORDER usage in xgbe_map_rx_buffer Message-ID: <20170531160422.GW27783@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tom, I have stumbled over the following construct in xgbe_map_rx_buffer order = max_t(int, PAGE_ALLOC_COSTLY_ORDER - 1, 0); which looks quite suspicious. Why does it PAGE_ALLOC_COSTLY_ORDER - 1? And why do you depend on PAGE_ALLOC_COSTLY_ORDER at all? Thanks! -- Michal Hocko SUSE Labs