Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp5824539rwl; Sun, 8 Jan 2023 23:39:09 -0800 (PST) X-Google-Smtp-Source: AMrXdXvERj9pA0IaQ4uImqHV3A96ytDKxMK/Fq9EZw3gyc2VW9wkTTCHqeVR0g1lL7T0saZsvdj1 X-Received: by 2002:a17:907:a08d:b0:7c1:6986:2b7c with SMTP id hu13-20020a170907a08d00b007c169862b7cmr49078871ejc.8.1673249949216; Sun, 08 Jan 2023 23:39:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673249949; cv=none; d=google.com; s=arc-20160816; b=N3SiqavVYIbxuSZ2rlCpFhQTuli/4B+Xd1Y3a2BFtPzm+/4nOgASSoUnvkxi/PUlSz opcMhAlnfZz6WvBlsEtZUAMY7ibU7VJo2dEwFD2uJoDNYBMTnisa1cdp+6mZAiMM12qF NbNk431oF35Lv0DhRwj6NKNiByW5HnC5jEHq6Lyk1FLeOcsSzjZ6DvQCXcbfhnW5n2Iw jdDULm4uKe3skayvEAiEeqiurJYdg++SOqX88vGwHAZBR9SkYyIvnDzxljukrGv+vpjg k4MunQwmV2fogBqR63dzcGIuYMha1UkTcSEtGePlH4366RybfMBoHlz71VU48avuR1k0 zIFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=zxwScJRBUIHFDjZqphAZcLPdTwye6P2TqNVQXbMZbxw=; b=MIVUsWypndBllux0hw5v1nX4ahXWBC6aSAQbT1TYMAF6QYpqMFe5TkwAHww1Nh8aSV UQpbdYIFeHrFkDTwuA9FoTV+w78fYq1l3M0k7cCOfGD2ujcTgbUZg4R2ze7sI9tAKEmk vBC7mjkc4hysDxSJ0Unh+sz/x131lA+WJs+v9p7QUCF47n8M+6+K+1gMEby5uovKhfo1 eSD0K6/T7SV6j7GmdhyQmAFopD4npnxFtT77IpxCkCJTFRh2inBPmHdDew8wxdfWlXXI Jlm9ObDYlJiz03euH0mcKjEkkdLcYYlCVG/GnPIF7XhEWH5g2EI862wWOkQY7PVeEFqE 85lw== 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 xd9-20020a170907078900b007c10e7a7628si8295481ejb.839.2023.01.08.23.38.42; Sun, 08 Jan 2023 23:39:09 -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 S236133AbjAIHiK (ORCPT + 99 others); Mon, 9 Jan 2023 02:38:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236325AbjAIHiJ (ORCPT ); Mon, 9 Jan 2023 02:38:09 -0500 Received: from formenos.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E1DE012ABC; Sun, 8 Jan 2023 23:38:05 -0800 (PST) Received: from loth.rohan.me.apana.org.au ([192.168.167.2]) by formenos.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1pEmir-00FVEa-N9; Mon, 09 Jan 2023 15:37:34 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Mon, 09 Jan 2023 15:37:33 +0800 Date: Mon, 9 Jan 2023 15:37:33 +0800 From: Herbert Xu To: Christophe Leroy Cc: Christoph Hellwig , Catalin Marinas , Ard Biesheuvel , Will Deacon , Marc Zyngier , Arnd Bergmann , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , Linux Memory Management List , Linux ARM , Linux Kernel Mailing List , "David S. Miller" , Linux Crypto Mailing List Subject: Re: [PATCH] crypto: talitos - Remove GFP_DMA and add DMA alignment padding Message-ID: References: <07259416-84bb-c264-dd8a-5bb3706b8c49@csgroup.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07259416-84bb-c264-dd8a-5bb3706b8c49@csgroup.eu> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS 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 Mon, Jan 09, 2023 at 07:18:27AM +0000, Christophe Leroy wrote: > > Doesn't GFP_DMA guarantees that the provided memory is addressable for > DMA ? Or do we assume that all memory returned by kmalloc can be used > for DMA ? No it does not. Please refer to the DMI API documentation. > kmalloc() already returns not DMA aligned memory, why does it becomes a > problem now ? As it stands kmalloc on arm64 returns DMA-aligned memory. This will soon no longer be the case. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt