Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp263542rwb; Thu, 11 Aug 2022 00:37:18 -0700 (PDT) X-Google-Smtp-Source: AA6agR623vCL5lA2Ejvo1iAwALou8WvOwcRy1rVCItZ79L9cfD18TKZctV+1E3pwBAKbBFTNl8vx X-Received: by 2002:a17:906:ef90:b0:730:9af7:5702 with SMTP id ze16-20020a170906ef9000b007309af75702mr23402341ejb.107.1660203437772; Thu, 11 Aug 2022 00:37:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660203437; cv=none; d=google.com; s=arc-20160816; b=fdx7A9IJF8Owz0DtgTGep8MZIQr+P24RgP28t6efYK9bo1JF91GjP5hRIIrKUUyOf6 iwy4/GW3SOX981FzmCWAL+O/iaTfQ4dw7QQSA1oUdmMBKxLdzSb2/b5uFi2ITfcW2ArX +HfVflnnGpQAZcRXcH2NER8fueAvXkQUJ7NHXSuzNZV7aO8W+5DBpWjIt7zxePiEjtRr kchDyy9X+rxi+Of5dgCWhBH8jFpYt/ZeaxuE+wRmugehkjJrgIeSulxbb5mRWkulFPGf mqKjlirAVxVIo4V82Ipw4bR+nYf11YCHyZOQ6L6j9GSlPtLFBrpAYohKMkUWNSOw1Jc8 AgHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=L7eK97qylRT4TIVKbS2J7JUrZY2NoG4/0xGvR9WF1co=; b=mauBjaABMCFkDE0CPlRZ2YjIsEQUHwZaG1ZCySaSbJ9jzF0OHo88ujFOTj7+wkBAeB E2SlVWwDqJ83clxX4jXFPVmC8jTbNsaLDGKkdjHLFY3Z1hpX8wgKMNy+3NELaemybsTs 6Q5lQ9ibp8UfsfboBH+jVKFLIzWP94FMzVoUgHdG1lQyV3PdTHvPAw7cUNPKoeZZsZ4r NAx94qyREWDAFO5bcqGz9FTOPdsKYizCyykYWb2TKxZ9tWsjVnQ5yZV20GBZpg+8cRM8 iaKYFk30U7UEzw6WIufn6GDoupvFQlU4TImpzdpA2o/NhBa2IWrllcRMx30ntmOLIhfU nvCQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v19-20020aa7d9d3000000b0043c2f94a3adsi12261501eds.592.2022.08.11.00.36.51; Thu, 11 Aug 2022 00:37:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234421AbiHKHfB (ORCPT + 99 others); Thu, 11 Aug 2022 03:35:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40156 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234253AbiHKHfA (ORCPT ); Thu, 11 Aug 2022 03:35:00 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DFD178E0EA for ; Thu, 11 Aug 2022 00:34:58 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 1616868AA6; Thu, 11 Aug 2022 09:34:55 +0200 (CEST) Date: Thu, 11 Aug 2022 09:34:54 +0200 From: Christoph Hellwig To: Michal Hocko Cc: Baoquan He , Christoph Hellwig , Andrew Morton , John Donnelly , David Hildenbrand , linux-mm@kvack.org, LKML Subject: Re: [PATCH] dma/pool: do not complain if DMA pool is not allocated Message-ID: <20220811073454.GD13886@lst.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 05, 2022 at 07:37:16PM +0200, Michal Hocko wrote: > GFP_DMA is a misnomer. It doesn't really say that the allocation should > be done for actual DMA. GFP_DMA really says allocate from ZONE_DMA. Yes. But in practice that either is to do DMA of some form, including the s390 variant not using the dma api, or completely stupid cargo cult code. > It > is my understanding that all actual DMA users should use a dedicated dma > allocation APIs which should do the right thing wrt. address constrains. Yes. And we were at a point where we got to that, but it seems somewhat recently a lot of people added completely stupid GFP_DMA kmallocs in the all over the crypto drivers. Sigh...