Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp3126462imd; Mon, 29 Oct 2018 02:01:25 -0700 (PDT) X-Google-Smtp-Source: AJdET5djaS1m1kaLg1edJWp4OrPelurX4tJLgnRn4TfyyDku+Sw2I+7QapUNSq490dXYVYmr6ASe X-Received: by 2002:a62:be1a:: with SMTP id l26-v6mr14595860pff.204.1540803685832; Mon, 29 Oct 2018 02:01:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540803685; cv=none; d=google.com; s=arc-20160816; b=fidETZCJBOXpGR0m2QHFr5HFkufnGR92aG7tU0KKeXB+H9Ai80ocCFJBjRfsPJQDjg Mf6+DgWwIybVEecpvBpwuNspKP+5H97uMPFx1hlnunTej5POtm+A7V6mClGyUwtzxwzm FSx+oCx8Ty9k6VXI1eVm9loyo0GTXDV25tDlrJTtvwqgBqiCLYT//uswLYjRyxrTzK2z KYNnUD4BGdRaeUGkXy3rnwcCxtt2PP3Zgjm+RcKAAs9sX4upmI70IHMs0Etx0+2tkZ+Q F4DRgcuyuQ0r02SYyJxRpFfPE9/vbb+FvV1lc8OBYG5fAi00CKaVdpztkFJ0Qv1XBqAU 1frg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6F1jdLQvbYc2M7pR7Vp2y7rafmxkVB11Eppe97B/ATo=; b=wgTyCgdVs/UX/hHB0whKBZkUcL99Tna5lBzRC6EHwJHlYKN2yl3MgULfndKL2J1uTk Tf6kDqDnHrFUWyOSGIACYVZPRmCARQDs8IFEavpEtjl8S4jsl9n62S1KTbrj1an6CzHO s/1wRwHNhpXr6+q8kJurYxIVYxLS8/l8DZroz53tg8lQkO93gAArjnORAy2OPfA7QV0C bwmtqbUBjvIBxVU+vEMUB5yH+BfYZo+zA8D1C7ryvg8rm4lp1QhMTiYCgO0M8puv9W+6 dafQL3zj9sUgE7RXrmtd+KLpwNNOnJCdBFErMGjALuIwqKT69ESnFRPUer2sW9kzW7/w kVOg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w19-v6si19709979pgl.278.2018.10.29.02.01.09; Mon, 29 Oct 2018 02:01:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729580AbeJ2RsU (ORCPT + 99 others); Mon, 29 Oct 2018 13:48:20 -0400 Received: from mx2.suse.de ([195.135.220.15]:49418 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729565AbeJ2RsU (ORCPT ); Mon, 29 Oct 2018 13:48:20 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id EDD9BAF77; Mon, 29 Oct 2018 09:00:35 +0000 (UTC) Date: Mon, 29 Oct 2018 10:00:35 +0100 From: Michal Hocko To: Balbir Singh Cc: Andrew Morton , Mel Gorman , Vlastimil Babka , David Rientjes , Andrea Argangeli , Zi Yan , Stefan Priebe - Profihost AG , "Kirill A. Shutemov" , linux-mm@kvack.org, LKML , Andrea Arcangeli , Stable tree Subject: Re: [PATCH 1/2] mm: thp: relax __GFP_THISNODE for MADV_HUGEPAGE mappings Message-ID: <20181029090035.GE32673@dhcp22.suse.cz> References: <20180925120326.24392-1-mhocko@kernel.org> <20180925120326.24392-2-mhocko@kernel.org> <20181029051752.GB16399@350D> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181029051752.GB16399@350D> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 29-10-18 16:17:52, Balbir Singh wrote: [...] > I wonder if alloc_pool_huge_page() should also trim out it's logic > of __GFP_THISNODE for the same reasons as mentioned here. I like > that we round robin to alloc the pool pages, but __GFP_THISNODE > might be an overkill for that case as well. alloc_pool_huge_page uses __GFP_THISNODE for a different reason than THP. We really do want to allocated for a per-node pool. THP can fallback or use a different node. These hugetlb allocations might be disruptive and that is an expected behavior because this is an explicit requirement from an admin to pre-allocate large pages for the future use. __GFP_RETRY_MAYFAIL just underlines that requirement. Maybe the compaction logic could be improved and that might be a shared goal with future changes though. -- Michal Hocko SUSE Labs