Received: by 10.192.165.148 with SMTP id m20csp705991imm; Wed, 2 May 2018 07:32:20 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqWffJg8PycY3DQ7GTTalnNqRqMIPUS5frf1OBiTS0LiI1LgvAJB7/N2fXlsd+3DOW4YKAJ X-Received: by 2002:a65:65ce:: with SMTP id y14-v6mr16373357pgv.137.1525271540204; Wed, 02 May 2018 07:32:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525271540; cv=none; d=google.com; s=arc-20160816; b=CD/XqM6vGyhfsbomaMzxXW2UU8P3Lcr56ZMzLNzecCJB9+P6B4Uyk0t+sAoG2ONZe6 CqOTtmrIeIXe39Kms7p/oe2cgb5+iMqPgJxhSzT3uviDPtd3f4RVc/aAimHr4FNJ8cJn K5G9NTOTiUhYUsiOXNJVf/9MAB58R2m9vRVwcVQYnbzi6T627RTPyQESGEfFZF8JEoBM lCFAexEF6fImp6RWh4/DOgpjWgmZxNefeO1gVIokZARp6BVOcHviJQ0r+G0Xbs4l/dmc Jx4kV/c0lPxm6mKWLklbdj+8WhC9BdjP+2AFtg7G+2iNgRNB+D50wfIpvvjWEz3jS6pU /4iQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=uj7kItryYAYcTE6odQxEiyK8VDbYd9x0muaBr1FfyfE=; b=G84JV0pMJL2yPa3oj7Y3BuHyNoql1/M1dMGF8EsayI83aMuuaCHYQPTMEs64Nzb2xg AZMUy4Yfrf7GnLzDOflmCph9Ox7oMwygSfZJHOmyr3TfIlXDqD6KZ83zufeIrRbfETd4 LQxkAbTSs9eB1hzOoUVaH9rxJo5tnl59YOCrY9TQKgPyQgc7hrFJO0iqo6mfxGcljiTK RHPqOEe9LinBulXWTQ1IVkLNN7GOTRKIHYSny6JQjCjf0t+XR1Qq+9mjX8jVVNffdu4E erYKzTyw0HCWQoT5KcsPZhieNl/JLSiCC6FLGszu/WtlI/+un2Z5Yxu7WZ82M9FvXcFG S4dQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a5-v6si11557143pll.123.2018.05.02.07.32.05; Wed, 02 May 2018 07:32:20 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751678AbeEBObO (ORCPT + 99 others); Wed, 2 May 2018 10:31:14 -0400 Received: from mail.netline.ch ([148.251.143.178]:36142 "EHLO netline-mail3.netline.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751011AbeEBObN (ORCPT ); Wed, 2 May 2018 10:31:13 -0400 Received: from localhost (localhost [127.0.0.1]) by netline-mail3.netline.ch (Postfix) with ESMTP id EF1DE2A6049; Wed, 2 May 2018 16:31:11 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at netline-mail3.netline.ch Received: from netline-mail3.netline.ch ([127.0.0.1]) by localhost (netline-mail3.netline.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h4MjOY76c9Vi; Wed, 2 May 2018 16:31:11 +0200 (CEST) Received: from thor (145.233.60.188.dynamic.wline.res.cust.swisscom.ch [188.60.233.145]) by netline-mail3.netline.ch (Postfix) with ESMTPSA id 564812A6045; Wed, 2 May 2018 16:31:10 +0200 (CEST) Received: from localhost ([::1]) by thor with esmtp (Exim 4.91) (envelope-from ) id 1fDsmj-0000Mn-Iq; Wed, 02 May 2018 16:31:09 +0200 Subject: Re: [PATCH] swiotlb: Fix inversed DMA_ATTR_NO_WARN test To: Christoph Hellwig , Daniel Vetter Cc: Konrad Rzeszutek Wilk , Linux Kernel Mailing List , dri-devel , =?UTF-8?Q?Christian_K=c3=b6nig?= , iommu@lists.linux-foundation.org References: <20180501132411.2311-1-michel@daenzer.net> <786ca83f-45c4-264b-2aef-d84fb18d3d28@gmail.com> <20180502124151.GA22857@lst.de> From: =?UTF-8?Q?Michel_D=c3=a4nzer?= Message-ID: <1066dfa2-2f78-815d-c65a-9d09eb35458c@daenzer.net> Date: Wed, 2 May 2018 16:31:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180502124151.GA22857@lst.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-05-02 02:41 PM, Christoph Hellwig wrote: > On Wed, May 02, 2018 at 02:18:56PM +0200, Daniel Vetter wrote: >> Other dma-api backends like cma just shut up when __GFP_NOWARN is >> passed. And afaiui Christoph Hellwig has plans to nuke the DMA_ATTR >> stuff (or at least clean it up) - should we just remove >> DMA_ATTR_NO_WARN and instead only look at __GFP_NOWARN? > > No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface > for dma allocations and just cause problems. I actually plan to > get rid of the gfp_t argument in dma_alloc_attrs sooner, and only > allow either GFP_KERNEL or GFP_DMA passed in dma_alloc_coherent. How about GFP_TRANSHUGE_LIGHT? TTM uses that to opportunistically allocate huge pages (GFP_TRANSHUGE can result in unacceptably long delays with memory pressure). -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer