From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C1AFAC3A5A7 for ; Tue, 6 Dec 2022 06:29:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=g3pGJWx1tp4fmaeeVq53zGMxL44AtiKdKsf+nNUFtqc=; b=Ekkjk4KEm1q+xd dcIETk/yyOKeAEsnqTUyN77BBI4uPypPufjDDNPg6QzuP1ybb7OXtZko9dCj4GauDOWkSi252dTdg F9xI6TSmJ5pZTfUhDn+cmETbPDQr7ZSGfoDVH1U67LftEpeAXfHHIgiqtXbk/Am81X2XxuBtI7BuM kuU9+zL9VHAugjARQrpLpYZGcTTerDnAlpaIEaQbXvK4W0inQAVQnCieuIFO3E1sWRzSDqQ/lBAxA VS/gvfYELKjWvkBsLgs9GfkibRNAblXZfsj0hsuA7m3jBD5Cget/i/gfC8310zzB4RsM+0UTc0vUF 0jSMWuw9Rusb1yA1hrIg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2RR5-0026me-RF; Tue, 06 Dec 2022 06:28:11 +0000 Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2RQs-0026iT-33; Tue, 06 Dec 2022 06:27:58 +0000 Date: Mon, 5 Dec 2022 22:27:58 -0800 From: Christoph Hellwig To: Herbert Xu 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 , LinuxKernelMailingList@gondor.apana.org.au, linux-kernel@vger.kernel.org, "David S. Miller" , Linux Crypto Mailing List Subject: Re: [PATCH 0/10] crypto: Driver conversions for DMA alignment Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Dec 06, 2022 at 12:13:52PM +0800, Herbert Xu wrote: > Yes they're clearly bogus. Basically they are saying they want > memory that is aligned sufficiently for DMA. So if Catalin's > patch-set will break this assumption, then all the GFP_DMA allocations > in drivers/crypto will need to be enlarged to take this into > account. But GFP_DMA never did do anything at all about alignment. It picks allocations from ZONE_DMA (which on x86 is the first 16MB only). _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel