Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp206963imm; Wed, 11 Jul 2018 00:37:17 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfTNbwnYyxrcrp+ziYyiO7uWdLiGGu+fnEsPQoO4F9zVlRfGJih1dGayiDktEbP5na/DDk4 X-Received: by 2002:a62:6a01:: with SMTP id f1-v6mr28999318pfc.156.1531294637026; Wed, 11 Jul 2018 00:37:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531294637; cv=none; d=google.com; s=arc-20160816; b=EV0pd+qco5x5TjVP6yy9GI1+30tfh6TXLZyJ7ZvtXW+vRJtNmO/IIcD7dMNOK6iZtu xN8gwp5dRN0oZDs6NESXsfse1CVDElr0xGleVJURO5HrtP2adYimPS0bwgHoJ+B+4Nxz Q8yWb+qd0NnBLv/lrzebYlX3HGFLtExJKIMmCEutjqSca3Zc8gwDY9BZaQv/Th70P7eu abax6S7aeG3PHjgPJlzffvawSRK96VK6wbRSRcbn2SejOzvwHuu3oKSLENTDzUzj0awx +r/ocJ1cUWf0hOeJKNT8hXrW7V+/3iZVl0fcheqtgjdxhk/BAF3WOdiXiMxhf3LMySwA +B2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=6U0pn6AhRTwBzPrYrAqCi9EEGjHJd9DpcVhBe07Rf6M=; b=JTulEp3zK239PVHHJlEBWUO6bvHk5iOqKh3oZsu6JS2i/HzydLAmwOIBZYp5e/B4qM TohfJhLz1Sxz4qX2dzgjyqejWKzrp9gVBY+KWaUrXZ1AZ3lc9pANtRC6tDUmTefiSLFH rveUtgl0kVrxU/8J2BEtvgaYUXKJfBkNn5Y92Pod+tX/F0lVOKzzki05c05/u1iS/dYz fLbNqE1BLTTG8joP5wY+V1m24RPFjYw8lE8ySGEs0KypQKDa4t7tDrdqVONI0SbDNLmQ LUjv/pDMZqWLgEugM/5S47yDldB3iacwHNSTJZU2/jCajA7oPNayP8BE4mHTGCYT6fiB Xo8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jEilD6dy; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t22-v6si18285242plo.263.2018.07.11.00.37.01; Wed, 11 Jul 2018 00:37:17 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jEilD6dy; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726337AbeGKHiY (ORCPT + 99 others); Wed, 11 Jul 2018 03:38:24 -0400 Received: from mail-wr1-f67.google.com ([209.85.221.67]:36450 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725808AbeGKHiY (ORCPT ); Wed, 11 Jul 2018 03:38:24 -0400 Received: by mail-wr1-f67.google.com with SMTP id h9-v6so17048956wro.3 for ; Wed, 11 Jul 2018 00:35:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6U0pn6AhRTwBzPrYrAqCi9EEGjHJd9DpcVhBe07Rf6M=; b=jEilD6dyHTjKhHnFpoQdkQKe0pZ15nbSFQZRAs18W6WZLufKolByMCmIT+vhy1jq5G euOBQvzEgzh3nUf+xIX4/OsFKP6jXLYA/ekC5nwLaMQtJRQiKJF2KrdGuwUfUCxDmAg/ GO0xMq4Q95zzGm6lwTgyz+fhu0XN5dQpv0CjwtrdHsNOF2eZXPF4A6QRoFEz4d4eoP3k ittCoMw9lb3lflmL3uUO2DDpyQmWe4c44NqAi0y4Z5Mgxxf/b3fpaPBtsM/ZmLOuJbCh kv/9N4IOnfN70mrI5/xwys1Gk1U+SQIOXlI5Wpcla5VtJpTdTnH3nS9MX3iP2br2uCLi 62Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6U0pn6AhRTwBzPrYrAqCi9EEGjHJd9DpcVhBe07Rf6M=; b=UHGKfYrZrb3ff+KiyRzLUXMeoHdigqGfpIv7CDvcNfs4LIP56JJsFtqFE19wyOE5Aa JDafKr9KGZ1JtwwxZVZGEDL6OQAtb4HAQFA1+dwpKPoFB/4HCHWZ7mfPu3UGKBlc0mt7 S+xCQMPobYE9Z3pmAkDMyB+3QfiFES5w8kN+2Kv1gxKspwWj2oPbpVKGbo759h+Wz4ak eXPKGdW9lPS4JzwCSpbrWEWw56rERImiUOdYMya5pigdF96OF0fwflyDggAikW5a9+XK 5qXESmRNDGjE8uyvMwsIYgCRkIDgRP/+QFXoTT/8s3O03Fq4rBlU2txTDYGdHVsKJbfa MkkA== X-Gm-Message-State: APt69E1BUf/Dr96hFze0SCQ51fKygdtajCiY1gl+AU2uWpdxBdKLubxk eoU7CoSGjxDLFaTqHYO6ZUULLaNAuBSdB2NeLdg= X-Received: by 2002:a5d:4c4c:: with SMTP id n12-v6mr19189950wrt.71.1531294529013; Wed, 11 Jul 2018 00:35:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:61c1:0:0:0:0:0 with HTTP; Wed, 11 Jul 2018 00:35:28 -0700 (PDT) In-Reply-To: <20180710095056.GE14284@dhcp22.suse.cz> References: <20180709121956.20200-1-m.szyprowski@samsung.com> <20180709122019eucas1p2340da484acfcc932537e6014f4fd2c29~-sqTPJKij2939229392eucas1p2j@eucas1p2.samsung.com> <20180710095056.GE14284@dhcp22.suse.cz> From: Joonsoo Kim Date: Wed, 11 Jul 2018 16:35:28 +0900 Message-ID: Subject: Re: [PATCH 1/2] mm/cma: remove unsupported gfp_mask parameter from cma_alloc() To: Michal Hocko Cc: Marek Szyprowski , Linux Memory Management List , LKML , linux-arm-kernel@lists.infradead.org, linuxppc-dev , iommu@lists.linux-foundation.org, Andrew Morton , Michal Nazarewicz , Joonsoo Kim , Vlastimil Babka , Christoph Hellwig , Russell King , Catalin Marinas , Will Deacon , Paul Mackerras , Benjamin Herrenschmidt , Chris Zankel , Martin Schwidefsky , Joerg Roedel , Sumit Semwal , Robin Murphy , Laura Abbott , linaro-mm-sig@lists.linaro.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-07-10 18:50 GMT+09:00 Michal Hocko : > On Tue 10-07-18 16:19:32, Joonsoo Kim wrote: >> Hello, Marek. >> >> 2018-07-09 21:19 GMT+09:00 Marek Szyprowski : >> > cma_alloc() function doesn't really support gfp flags other than >> > __GFP_NOWARN, so convert gfp_mask parameter to boolean no_warn parameter. >> >> Although gfp_mask isn't used in cma_alloc() except no_warn, it can be used >> in alloc_contig_range(). For example, if passed gfp mask has no __GFP_FS, >> compaction(isolation) would work differently. Do you have considered >> such a case? > > Does any of cma_alloc users actually care about GFP_NO{FS,IO}? I don't know. My guess is that cma_alloc() is used for DMA allocation so block device would use it, too. If fs/block subsystem initiates the request for the device, it would be possible that cma_alloc() is called with such a flag. Again, I don't know much about those subsystem so I would be wrong. Thanks.