Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp3988130iob; Tue, 17 May 2022 11:16:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyqqmZd5V6/CBngCgH8I2A5WPCs9dZ08WFwoQtslqKAQuwvbXSds4BfhYywYApGP4MduLtn X-Received: by 2002:a17:907:d05:b0:6f4:3729:8e36 with SMTP id gn5-20020a1709070d0500b006f437298e36mr20089105ejc.475.1652811412256; Tue, 17 May 2022 11:16:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652811412; cv=none; d=google.com; s=arc-20160816; b=EqWOl+ixa4GYU8/ehtICAXiwWpJ1FT0BWeJMp+E6XNpvSlGbyWL5CXENygEMRjUzc+ le/5mfHpn/NskTyFpC44glXowMcQzRiGLoruYoY0MlQEIXyKRxFuZwXAxU8QQWcc/9B9 VD551UDiYY2PIlk1N3nfTI6+ScwgzA62ydspeRpJ0ReOnkEn6b9vm5RKx7konNvruj71 u88kUBCDMW4++dCojwMCb8yHbSbEtNg0xKa7V3xlwvjdTxbU4pzCWsXH2kfgRhCEHb9m B+2eCXqMyurPEfhYLQBG5HZdEUxFt9PsGHXwNcnjV+x0mecj4QCyHmLuEvSSOlk4Th6L z0WA== 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=f0ty1kp8niXoZ00XfOxMzs+Aqa5UVWLACibcHCkeLC4=; b=ydX96KCF0Gellv+2pcKR78ISqISABpT6kxbw6MlkQL0uxRqJeDcyOYX+MT8Wknfz2D pqUlot3+tPKrFu77bFQiKAuf+GiluYhgSKfkGDcC7CB1V9GKdGn+0TTXBIev6jeU1wEl E3IUgF0nfnl9wtzdonHyCXpD5GspEFIzYXZGWzkxyw8I2p1U1D6io+tn9IGA9MMd4EF8 VJF4Dz22P/D+C6iGFsnFwjjA7sORkFcM0DhltASXBMznARipNrl4hGENIJ6gaswxFqon BiukX7eE/Imsu4uM6b9MERyWurKuogDIH0lKT4wQQ3X3eVsWeHERTRvvUCTKO27d5YlB 0GeA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-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 q12-20020a170906360c00b006e5b5e966d3si317114ejb.709.2022.05.17.11.16.25; Tue, 17 May 2022 11:16:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243435AbiEQIil (ORCPT + 99 others); Tue, 17 May 2022 04:38:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57364 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232605AbiEQIij (ORCPT ); Tue, 17 May 2022 04:38:39 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 641EF65BC for ; Tue, 17 May 2022 01:38:38 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 4240467373; Tue, 17 May 2022 10:38:35 +0200 (CEST) Date: Tue, 17 May 2022 10:38:34 +0200 From: Christoph Hellwig To: John Garry Cc: joro@8bytes.org, will@kernel.org, hch@lst.de, robin.murphy@arm.com, m.szyprowski@samsung.com, chenxiang66@hisilicon.com, thunder.leizhen@huawei.com, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, liyihang6@hisilicon.com Subject: Re: [RFC PATCH] dma-iommu: Add iommu_dma_max_mapping_size() Message-ID: <20220517083834.GA16965@lst.de> References: <1652706361-92557-1-git-send-email-john.garry@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1652706361-92557-1-git-send-email-john.garry@huawei.com> 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-kernel@vger.kernel.org On Mon, May 16, 2022 at 09:06:01PM +0800, John Garry wrote: > For streaming DMA mappings involving an IOMMU and whose IOVA len regularly > exceeds the IOVA rcache upper limit (meaning that they are not cached), > performance can be reduced. > > Add the IOMMU callback for DMA mapping API dma_max_mapping_size(), which > allows the drivers to know the mapping limit and thus limit the requested > IOVA lengths. > > This resolves the performance issue originally reported in [0] for a SCSI > HBA driver which was regularly mapping SGLs which required IOVAs in > excess of the IOVA caching limit. In this case the block layer limits the > max sectors per request - as configured in __scsi_init_queue() - which > will limit the total SGL length the driver tries to map and in turn limits > IOVA lengths requested. > > [0] https://lore.kernel.org/linux-iommu/20210129092120.1482-1-thunder.leizhen@huawei.com/ > > Signed-off-by: John Garry > --- > Sending as an RFC as iommu_dma_max_mapping_size() is a soft limit, and not > a hard limit which I expect is the semantics of dma_map_ops.max_mapping_size > > diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c > index 09f6e1c0f9c0..e2d5205cde37 100644 > --- a/drivers/iommu/dma-iommu.c > +++ b/drivers/iommu/dma-iommu.c > @@ -1442,6 +1442,21 @@ static unsigned long iommu_dma_get_merge_boundary(struct device *dev) > return (1UL << __ffs(domain->pgsize_bitmap)) - 1; > } > > + if (!domain) > + return 0; > + > + cookie = domain->iova_cookie; > + if (!cookie || cookie->type != IOMMU_DMA_IOVA_COOKIE) > + return 0; Can these conditions even be true here? > +static inline unsigned long iova_rcache_range(void) > +{ > + return 0; > +} Given that IOMMU_DMA select IOMMU_IOVA there is no need for this stub. Otherwise this looks sensible to me.