Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp7456079ybi; Thu, 1 Aug 2019 08:26:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqy+X2FoFOoRxbNtEvU2Jt2p3zfoDxKfaUSoYzsmhrfy8hAD6w7yRbMjeEkkKDBd9fM5a7No X-Received: by 2002:aa7:90c9:: with SMTP id k9mr52594863pfk.171.1564673202473; Thu, 01 Aug 2019 08:26:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564673202; cv=none; d=google.com; s=arc-20160816; b=SZeeCNlrPYXMcAJahhk0Ayb92xoJVKKVDMtzdlE+n92j/ur8I1O29JyWsgOUkghYVa elxHX8VhiEyYwPDCwlkOYvjcb1qU4zmmorsfJlHkK292vScl/tVDLCJUI+cHUJXlCDXt 0OeqvDHZXX7s1W7SpJDpaU4OjUHuS+/wkHRCLxQN5BgqLachK3+MAzBan8KiR+c2UE4w 5nrqpYiAo+kB7WuWkfi1A7d6o05mYmf38U7g0QpUkiT41szkTvIj6P0yQInRYNRKxicV 6qXaChfmqr7D/k0612rDG7TGZ2BKu9/MS58epAn7nZl6rzL63JQ3lo47hwSUS+AKpfFm 0wGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=9Krm7V9dm1DW1xERMxJYYqhRiT0zghcWUSHdiwkOOLk=; b=uJSE2kI3lbgnTCtp4dhW14PSDCpEsWKWph4pDVZ6kU2C2PU/GyYhfuqhxMHiQnmB/O CWCIIaUZqPVXW7B/T+5q8iXaekE9M8rCTyIM8Kow8VmpuyCbocGPQZhXMTL9OQu1jyck L5QJAiwcgbX3l2KiW1WnCRkPf4K00tB2hzxRTPq8LV9j2iA5Lq78LInHPuOecagvy//B iK7bSMC8EXB4YHJHic1LG9MwUcCo86AICbKfPrBfClSZdpGW96GuBndZ7YM5SC0h9gF/ XwFP88Pgy/8UVjJvw/zmWo9QmUa5zfREU2J45RCbgDLSyQ0CFTM+xQsF+iBPAbtGluer WMmw== 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 h31si19600170pgb.67.2019.08.01.08.26.27; Thu, 01 Aug 2019 08:26:42 -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 S1731779AbfHAOIZ (ORCPT + 99 others); Thu, 1 Aug 2019 10:08:25 -0400 Received: from verein.lst.de ([213.95.11.211]:43788 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731468AbfHAOIY (ORCPT ); Thu, 1 Aug 2019 10:08:24 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 7FDE168AFE; Thu, 1 Aug 2019 16:08:20 +0200 (CEST) Date: Thu, 1 Aug 2019 16:08:20 +0200 From: Christoph Hellwig To: Nicolas Saenz Julienne Cc: catalin.marinas@arm.com, hch@lst.de, wahrenst@gmx.net, marc.zyngier@arm.com, Robin Murphy , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, iommu@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, phill@raspberryi.org, f.fainelli@gmail.com, will@kernel.org, robh+dt@kernel.org, eric@anholt.net, mbrugger@suse.com, akpm@linux-foundation.org, frowand.list@gmail.com, m.szyprowski@samsung.com, linux-rpi-kernel@lists.infradead.org Subject: Re: [PATCH 8/8] mm: comment arm64's usage of 'enum zone_type' Message-ID: <20190801140820.GC23435@lst.de> References: <20190731154752.16557-1-nsaenzjulienne@suse.de> <20190731154752.16557-9-nsaenzjulienne@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190731154752.16557-9-nsaenzjulienne@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 31, 2019 at 05:47:51PM +0200, Nicolas Saenz Julienne wrote: > + * Architecture Limit > + * ---------------------------------- > + * parisc, ia64, sparc, arm64 <4G > + * s390, powerpc <2G > + * arm Various > + * alpha Unlimited or 0-16MB. > * > * i386, x86_64 and multiple other arches > - * <16M. > + * <16M. powerpc is also Various now, arm64 isn't really < 4G, ia64 only uses ZONE_DMA32 these days, and parisc doesn't seem to use neither ZONE_DMA nor ZONE_DMA32. Based on that I'm not sure the list really makes much sense. > */ > ZONE_DMA, > #endif > #ifdef CONFIG_ZONE_DMA32 > /* > - * x86_64 needs two ZONE_DMAs because it supports devices that are > - * only able to do DMA to the lower 16M but also 32 bit devices that > - * can only do DMA areas below 4G. > + * x86_64 and arm64 need two ZONE_DMAs because they support devices > + * that are only able to DMA a fraction of the 32 bit addressable > + * memory area, but also devices that are limited to that whole 32 bit > + * area. > */ > ZONE_DMA32, Maybe just say various architectures instead of mentioning specific ones? Something like "Some 64-bit platforms need.."