Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp1262792pxm; Wed, 23 Feb 2022 22:47:28 -0800 (PST) X-Google-Smtp-Source: ABdhPJxHgtXbG2SPsXG3js3HUZOKliFlwWfocsYn4465uIHVGunfK98cfh8FRscV26GnbccTQbQE X-Received: by 2002:a17:906:ae56:b0:6ce:375a:4b93 with SMTP id lf22-20020a170906ae5600b006ce375a4b93mr1113009ejb.189.1645685248273; Wed, 23 Feb 2022 22:47:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645685248; cv=none; d=google.com; s=arc-20160816; b=qUDseO7xbD+07loPLAZ0aqTHhzFEK0PP5dKC1V063HV432dAKmsrEv7RLaieSYSWuO Vt6TIQIXLFMKub4URILiy64yaRSNN9sHrib264frUeT21Cy9lpUhkJ2StifIutD9//6v jiSeA7c5qMmVgVpcG1jl9bJL55qZOtMpaiH2wQR5TpgWAtGC/X1b8yHVzlSNP6Ljtmh/ pcRpqeJvZxMVdCmcjzwlmmoSL0skxPCXMogTcxC/P6HBbPN/AZDeNSkPGZa9PB2Vqv4K /N9SElCxhkWlZ4kigUgptC7F3iLNLrcfFhh207qGOYOzUPE1qaHVNnljkzrLHu7Itn+p GVxQ== 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=bNP4BMS7nJ4Z30RXYtuxPMvh1GtCPhPRwFMQo+zF+hw=; b=M60wbRbaSzbTTQqOLJgarVPFdTEjDN+geAIBq03VHOj6QNhY+da3WsKBf56lWBVS8E agqHOuVG5LW289nDvq32m8pRAdYdcxpMkV0BwaIZluFdS+cexhyo1ziLRXJMhKBoCUL0 IcDtzkVr8UfwKv4151dhY7HwM70BG84/Xv+Jdxlx9yHLt3ETT0Jy0YTRuHHJ0Y7k0yr2 IUcqufG44LLqJx4OLxUiW28NrXZOFE56bskWTiJLS2paOeBN2YeGf7eneidk6sXZuMSE IUz61AGS+HCUNTS+3GhO60ZEgPius/YG5mVEXYlxzIY0dP4Q8m73z8wHoB3vhrXWX7RT k+ng== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 jg33si1312579ejc.669.2022.02.23.22.46.51; Wed, 23 Feb 2022 22:47:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-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-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231177AbiBXGeF (ORCPT + 99 others); Thu, 24 Feb 2022 01:34:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59660 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229838AbiBXGeE (ORCPT ); Thu, 24 Feb 2022 01:34:04 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1CC89AC915; Wed, 23 Feb 2022 22:33:35 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 3C97768AA6; Thu, 24 Feb 2022 07:33:30 +0100 (CET) Date: Thu, 24 Feb 2022 07:33:30 +0100 From: Christoph Hellwig To: Heiko Carstens Cc: Christoph Hellwig , Baoquan He , linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, cl@linux.com, 42.hyeyoo@gmail.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, vbabka@suse.cz, David.Laight@aculab.com, david@redhat.com, herbert@gondor.apana.org.au, davem@davemloft.net, linux-crypto@vger.kernel.org, steffen.klassert@secunet.com, netdev@vger.kernel.org, gor@linux.ibm.com, agordeev@linux.ibm.com, borntraeger@linux.ibm.com, svens@linux.ibm.com, linux-s390@vger.kernel.org, michael@walle.cc, linux-i2c@vger.kernel.org, wsa@kernel.org, Halil Pasic , Vineeth Vijayan Subject: Re: [PATCH 00/22] Don't use kmalloc() with GFP_DMA Message-ID: <20220224063330.GB20383@lst.de> References: <20220219005221.634-1-bhe@redhat.com> <20220222084422.GA6139@lst.de> 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-crypto@vger.kernel.org On Wed, Feb 23, 2022 at 08:18:08PM +0100, Heiko Carstens wrote: > > The long term goal is to remove ZONE_DMA entirely at least for > > architectures that only use the small 16MB ISA-style one. It can > > then be replaced with for example a CMA area and fall into a movable > > zone. I'd have to prototype this first and see how it applies to the > > s390 case. It might not be worth it and maybe we should replace > > ZONE_DMA and ZONE_DMA32 with a ZONE_LIMITED for those use cases as > > the amount covered tends to not be totally out of line for what we > > built the zone infrastructure. > > So probably I'm missing something; but for small systems where we > would only have ZONE_DMA, how would a CMA area within this zone > improve things? It would not, but more importantly we would not need it at all. The thinking here is really about the nasty 16MB ISA-style zone DMA. a 31-bit something rather different.