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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C7840CD68F6 for ; Tue, 10 Oct 2023 07:48:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1442552AbjJJHsW (ORCPT ); Tue, 10 Oct 2023 03:48:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35174 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1442419AbjJJHsU (ORCPT ); Tue, 10 Oct 2023 03:48:20 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4E6239E for ; Tue, 10 Oct 2023 00:48:19 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id BBE5968B05; Tue, 10 Oct 2023 09:48:16 +0200 (CEST) Date: Tue, 10 Oct 2023 09:48:16 +0200 From: Christoph Hellwig To: Jia He Cc: Christoph Hellwig , Marek Szyprowski , Robin Murphy , iommu@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] dma-mapping: fix dma_addressing_limited if dma_range_map can't cover all system RAM Message-ID: <20231010074816.GA9082@lst.de> References: <20231010020835.3678-1-justin.he@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231010020835.3678-1-justin.he@arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org dma_addressing_limited is called for every dma (direct) map, and this new code is way to heavy for that. We'll need to cache the information somehow.