Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp732702ybj; Thu, 7 May 2020 06:28:54 -0700 (PDT) X-Google-Smtp-Source: APiQypL7llUysIqUnrNZDmbg9FZt9Yra1v7OCPKSdmNe7PizF4/WekQOvKd+rcrS6fcxACSZgnYj X-Received: by 2002:aa7:c0d2:: with SMTP id j18mr12141740edp.283.1588858134011; Thu, 07 May 2020 06:28:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588858134; cv=none; d=google.com; s=arc-20160816; b=SZEZdNMK9L4EOL/Hzz70SsSfZS0gO4g5MKlILr1UM6ggxL6NQFmu5W80MvDPTieDPj 3TWbA7R7cVY+c03Tcwgafu7o8dEbQ0GtOSoBXpRkH8/Qly2kdCEXbmUu6ov7ElVCfOCi qPxEPP3TVp1zWi0RiG+c8YRWus6zIWTCpacS7D6WHVSpwScNpceYJrzJwnLUrBzb5rzx NJHuyR0GLXVdRQdk+CNcO3hK3HTEJZi/kaYLa5XQ6+0TOSUd+JggGhLRCsoHKfQNJ9yr ZTU4RBddGPPI5Iwq3Z/OMR6dHd21Z9AYeKBL+jJBdN9K6GuWNB0LSqqdUX6vRm/3MI1e 3DMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=YxRsHOcOtE+xF0ywLt1Znjg+xBJ3VBnxOYjbqCsNpNY=; b=KFlzgBuJvM+B9wgtZCZxpiub7ZOQTulk0trLEpOx3NdvH7l3kR0JYK2Le9QAJ0wggJ Senue7iMKQzAkNS6jDrUj1ZEL23ke9iad06hCeMG+tKTQG27Zt4bBN0WQTdTO21CHbG4 JiG9qhBQrgSNBna83BNdW0J3LT2vwuK78N8roHjiwD84/cBM8lpszhX3+IbuJkpe/qVn 3CsNpsn8cjPa+Q2dU8hn6OpVnx6H9/ysXtKjmEFHiWSxGAQXHsykpYoUBgk4Gk6CwcBn /uGwCSHV1ZPGE5VOFmeRHMcv8auYtzVs0RtSdBoK5mDF8J55eJlQxVbUoYwhpoASzlys cKeg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id di13si3028573edb.419.2020.05.07.06.28.26; Thu, 07 May 2020 06:28:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726480AbgEGNYG (ORCPT + 99 others); Thu, 7 May 2020 09:24:06 -0400 Received: from foss.arm.com ([217.140.110.172]:59298 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725848AbgEGNYF (ORCPT ); Thu, 7 May 2020 09:24:05 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 05D9CD6E; Thu, 7 May 2020 06:24:05 -0700 (PDT) Received: from [10.57.36.85] (unknown [10.57.36.85]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 01DA23F68F; Thu, 7 May 2020 06:24:03 -0700 (PDT) Subject: Re: [PATCH] iommu/iova: Retry from last rb tree node if iova search fails To: vjitta@codeaurora.org, joro@8bytes.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Cc: vinmenon@codeaurora.org, kernel-team@android.com References: <1588795317-20879-1-git-send-email-vjitta@codeaurora.org> From: Robin Murphy Message-ID: Date: Thu, 7 May 2020 14:24:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <1588795317-20879-1-git-send-email-vjitta@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-05-06 9:01 pm, vjitta@codeaurora.org wrote: > From: Vijayanand Jitta > > When ever a new iova alloc request comes iova is always searched > from the cached node and the nodes which are previous to cached > node. So, even if there is free iova space available in the nodes > which are next to the cached node iova allocation can still fail > because of this approach. > > Consider the following sequence of iova alloc and frees on > 1GB of iova space > > 1) alloc - 500MB > 2) alloc - 12MB > 3) alloc - 499MB > 4) free - 12MB which was allocated in step 2 > 5) alloc - 13MB > > After the above sequence we will have 12MB of free iova space and > cached node will be pointing to the iova pfn of last alloc of 13MB > which will be the lowest iova pfn of that iova space. Now if we get an > alloc request of 2MB we just search from cached node and then look > for lower iova pfn's for free iova and as they aren't any, iova alloc > fails though there is 12MB of free iova space. Yup, this could definitely do with improving. Unfortunately I think this particular implementation is slightly flawed... > To avoid such iova search failures do a retry from the last rb tree node > when iova search fails, this will search the entire tree and get an iova > if its available > > Signed-off-by: Vijayanand Jitta > --- > drivers/iommu/iova.c | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c > index 0e6a953..2985222 100644 > --- a/drivers/iommu/iova.c > +++ b/drivers/iommu/iova.c > @@ -186,6 +186,7 @@ static int __alloc_and_insert_iova_range(struct iova_domain *iovad, > unsigned long flags; > unsigned long new_pfn; > unsigned long align_mask = ~0UL; > + bool retry = false; > > if (size_aligned) > align_mask <<= fls_long(size - 1); > @@ -198,6 +199,8 @@ static int __alloc_and_insert_iova_range(struct iova_domain *iovad, > > curr = __get_cached_rbnode(iovad, limit_pfn); > curr_iova = rb_entry(curr, struct iova, node); > + > +retry_search: > do { > limit_pfn = min(limit_pfn, curr_iova->pfn_lo); > new_pfn = (limit_pfn - size) & align_mask; > @@ -207,6 +210,14 @@ static int __alloc_and_insert_iova_range(struct iova_domain *iovad, > } while (curr && new_pfn <= curr_iova->pfn_hi); > > if (limit_pfn < size || new_pfn < iovad->start_pfn) { > + if (!retry) { > + curr = rb_last(&iovad->rbroot); Why walk when there's an anchor node there already? However... > + curr_iova = rb_entry(curr, struct iova, node); > + limit_pfn = curr_iova->pfn_lo; ...this doesn't look right, as by now we've lost the original limit_pfn supplied by the caller, so are highly likely to allocate beyond the range our caller asked for. In fact AFAICS we'd start allocating from directly directly below the anchor node, beyond the end of the entire address space. The logic I was imagining we want here was something like the rapidly hacked up (and untested) diff below. Thanks, Robin. ----->8----- diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c index 0e6a9536eca6..3574c19272d6 100644 --- a/drivers/iommu/iova.c +++ b/drivers/iommu/iova.c @@ -186,6 +186,7 @@ static int __alloc_and_insert_iova_range(struct iova_domain *iovad, unsigned long flags; unsigned long new_pfn; unsigned long align_mask = ~0UL; + unsigned long alloc_hi, alloc_lo; if (size_aligned) align_mask <<= fls_long(size - 1); @@ -196,17 +197,27 @@ static int __alloc_and_insert_iova_range(struct iova_domain *iovad, size >= iovad->max32_alloc_size) goto iova32_full; + alloc_hi = IOVA_ANCHOR; + alloc_lo = iovad->start_pfn; +retry: curr = __get_cached_rbnode(iovad, limit_pfn); curr_iova = rb_entry(curr, struct iova, node); + if (alloc_hi < curr_iova->pfn_hi) { + alloc_lo = curr_iova->pfn_hi; + alloc_hi = limit_pfn; + } + do { - limit_pfn = min(limit_pfn, curr_iova->pfn_lo); - new_pfn = (limit_pfn - size) & align_mask; + alloc_hi = min(alloc_hi, curr_iova->pfn_lo); + new_pfn = (alloc_hi - size) & align_mask; prev = curr; curr = rb_prev(curr); curr_iova = rb_entry(curr, struct iova, node); } while (curr && new_pfn <= curr_iova->pfn_hi); - if (limit_pfn < size || new_pfn < iovad->start_pfn) { + if (limit_pfn < size || new_pfn < alloc_lo) { + if (alloc_lo == iovad->start_pfn) + goto retry; iovad->max32_alloc_size = size; goto iova32_full; }