From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755779AbbHYPsr (ORCPT ); Tue, 25 Aug 2015 11:48:47 -0400 Received: from mx2.suse.de ([195.135.220.15]:46967 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755685AbbHYPsp (ORCPT ); Tue, 25 Aug 2015 11:48:45 -0400 Subject: Re: [PATCH 07/12] mm, page_alloc: Distinguish between being unable to sleep, unwilling to sleep and avoiding waking kswapd To: Mel Gorman , Andrew Morton References: <1440418191-10894-1-git-send-email-mgorman@techsingularity.net> <1440418191-10894-8-git-send-email-mgorman@techsingularity.net> Cc: Johannes Weiner , Rik van Riel , David Rientjes , Joonsoo Kim , Michal Hocko , Linux-MM , LKML From: Vlastimil Babka Message-ID: <55DC8E5B.9050304@suse.cz> Date: Tue, 25 Aug 2015 17:48:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1440418191-10894-8-git-send-email-mgorman@techsingularity.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/24/2015 02:09 PM, Mel Gorman wrote: > The first key hazard to watch out for is callers that removed __GFP_WAIT > and was depending on access to atomic reserves for inconspicuous reasons. > In some cases it may be appropriate for them to use __GFP_HIGH. Hm so I think this hazard should be expanded. If such caller comes from interrupt and doesn't use __GFP_ATOMIC, the ALLOC_CPUSET with restrictions taken from the interrupted process will also apply to him?