From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751568AbcGRFrs (ORCPT ); Mon, 18 Jul 2016 01:47:48 -0400 Received: from LGEAMRELO12.lge.com ([156.147.23.52]:51184 "EHLO lgeamrelo12.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750982AbcGRFrq (ORCPT ); Mon, 18 Jul 2016 01:47:46 -0400 X-Original-SENDERIP: 156.147.1.125 X-Original-MAILFROM: iamjoonsoo.kim@lge.com X-Original-SENDERIP: 10.177.222.138 X-Original-MAILFROM: iamjoonsoo.kim@lge.com Date: Mon, 18 Jul 2016 14:51:50 +0900 From: Joonsoo Kim To: Xishi Qiu Cc: David Rientjes , Andrew Morton , Vlastimil Babka , Naoya Horiguchi , Linux MM , LKML Subject: Re: [PATCH 1/2] mem-hotplug: use GFP_HIGHUSER_MOVABLE in, alloc_migrate_target() Message-ID: <20160718055150.GF9460@js1304-P5Q-DELUXE> References: <57884EAA.9030603@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57884EAA.9030603@huawei.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 15, 2016 at 10:47:06AM +0800, Xishi Qiu wrote: > alloc_migrate_target() is called from migrate_pages(), and the page > is always from user space, so we can add __GFP_HIGHMEM directly. No, all migratable pages are not from user space. For example, blockdev file cache has __GFP_MOVABLE and migratable but it has no __GFP_HIGHMEM and __GFP_USER. And, zram's memory isn't GFP_HIGHUSER_MOVABLE but has __GFP_MOVABLE. Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f71.google.com (mail-pa0-f71.google.com [209.85.220.71]) by kanga.kvack.org (Postfix) with ESMTP id DE0E56B0253 for ; Mon, 18 Jul 2016 01:47:45 -0400 (EDT) Received: by mail-pa0-f71.google.com with SMTP id hh10so303835385pac.3 for ; Sun, 17 Jul 2016 22:47:45 -0700 (PDT) Received: from lgeamrelo12.lge.com (LGEAMRELO12.lge.com. [156.147.23.52]) by mx.google.com with ESMTP id gk9si24896747pac.182.2016.07.17.22.47.44 for ; Sun, 17 Jul 2016 22:47:45 -0700 (PDT) Date: Mon, 18 Jul 2016 14:51:50 +0900 From: Joonsoo Kim Subject: Re: [PATCH 1/2] mem-hotplug: use GFP_HIGHUSER_MOVABLE in, alloc_migrate_target() Message-ID: <20160718055150.GF9460@js1304-P5Q-DELUXE> References: <57884EAA.9030603@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57884EAA.9030603@huawei.com> Sender: owner-linux-mm@kvack.org List-ID: To: Xishi Qiu Cc: David Rientjes , Andrew Morton , Vlastimil Babka , Naoya Horiguchi , Linux MM , LKML On Fri, Jul 15, 2016 at 10:47:06AM +0800, Xishi Qiu wrote: > alloc_migrate_target() is called from migrate_pages(), and the page > is always from user space, so we can add __GFP_HIGHMEM directly. No, all migratable pages are not from user space. For example, blockdev file cache has __GFP_MOVABLE and migratable but it has no __GFP_HIGHMEM and __GFP_USER. And, zram's memory isn't GFP_HIGHUSER_MOVABLE but has __GFP_MOVABLE. Thanks. -- 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