From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, <vjitta@codeaurora.org>,
<joro@8bytes.org>, <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Cc: <vinmenon@codeaurora.org>, <kernel-team@android.com>
Subject: Re: [PATCH v5 2/2] iommu/iova: Free global iova rcache on iova alloc failure
Date: Tue, 3 Nov 2020 14:31:20 +0000 [thread overview]
Message-ID: <e1e5b24a-512b-7279-8341-7f4495718ece@huawei.com> (raw)
In-Reply-To: <ff318311-77e8-b235-37dd-7b1b5f5d8ed9@arm.com>
On 03/11/2020 12:35, Robin Murphy wrote:
> On 2020-09-30 08:44, vjitta@codeaurora.org wrote:
>> From: Vijayanand Jitta <vjitta@codeaurora.org>
>>
>> When ever an iova alloc request fails we free the iova
>> ranges present in the percpu iova rcaches and then retry
>> but the global iova rcache is not freed as a result we could
>> still see iova alloc failure even after retry as global
>> rcache is holding the iova's which can cause fragmentation.
>> So, free the global iova rcache as well and then go for the
>> retry.
>
If we do clear all the CPU rcaches, it would nice to have something
immediately available to replenish, i.e. use the global rcache, instead
of flushing it, if that is not required...
> This looks reasonable to me - it's mildly annoying that we end up with
> so many similar-looking functions,
Well I did add a function to clear all CPU rcaches here, if you would
like to check:
https://lore.kernel.org/linux-iommu/1603733501-211004-2-git-send-email-john.garry@huawei.com/
> but the necessary differences are
> right down in the middle of the loops so nothing can reasonably be
> factored out :(
>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
>
>> Signed-off-by: Vijayanand Jitta <vjitta@codeaurora.org>
>> ---
>> drivers/iommu/iova.c | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/drivers/iommu/iova.c b/drivers/iommu/iova.c
>> index c3a1a8e..faf9b13 100644
>> --- a/drivers/iommu/iova.c
>> +++ b/drivers/iommu/iova.c
>> @@ -25,6 +25,7 @@ static void init_iova_rcaches(struct iova_domain
>> *iovad);
>> static void free_iova_rcaches(struct iova_domain *iovad);
>> static void fq_destroy_all_entries(struct iova_domain *iovad);
>> static void fq_flush_timeout(struct timer_list *t);
>> +static void free_global_cached_iovas(struct iova_domain *iovad);
a thought: It would be great if the file could be rearranged at some
point where we don't require so many forward declarations.
>> void
>> init_iova_domain(struct iova_domain *iovad, unsigned long granule,
>> @@ -442,6 +443,7 @@ alloc_iova_fast(struct iova_domain *iovad,
>> unsigned long size,
>> flush_rcache = false;
>> for_each_online_cpu(cpu)
>> free_cpu_cached_iovas(cpu, iovad);
>> + free_global_cached_iovas(iovad);
>> goto retry;
>> }
>> @@ -1057,5 +1059,26 @@ void free_cpu_cached_iovas(unsigned int cpu,
>> struct iova_domain *iovad)
>> }
>> }
>> +/*
>> + * free all the IOVA ranges of global cache
>> + */
>> +static void free_global_cached_iovas(struct iova_domain *iovad)
>> +{
>> + struct iova_rcache *rcache;
>> + unsigned long flags;
>> + int i, j;
>> +
>> + for (i = 0; i < IOVA_RANGE_CACHE_MAX_SIZE; ++i) {
>> + rcache = &iovad->rcaches[i];
>> + spin_lock_irqsave(&rcache->lock, flags);
>> + for (j = 0; j < rcache->depot_size; ++j) {
>> + iova_magazine_free_pfns(rcache->depot[j], iovad);
>> + iova_magazine_free(rcache->depot[j]);
>> + rcache->depot[j] = NULL;
I don't think that NULLify is strictly necessary
>> + }
>> + rcache->depot_size = 0;
>> + spin_unlock_irqrestore(&rcache->lock, flags);
>> + }
>> +}
>> MODULE_AUTHOR("Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>");
>> MODULE_LICENSE("GPL");
>>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
> .
next prev parent reply other threads:[~2020-11-03 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:44 [PATCH v5 1/2] iommu/iova: Retry from last rb tree node if iova search fails vjitta
2020-09-30 7:44 ` [PATCH v5 2/2] iommu/iova: Free global iova rcache on iova alloc failure vjitta
2020-10-20 9:18 ` Vijayanand Jitta
2020-11-03 12:35 ` Robin Murphy
2020-11-03 14:31 ` John Garry [this message]
2020-11-03 15:59 ` Robin Murphy
2020-11-09 11:12 ` John Garry
2020-10-20 9:17 ` [PATCH v5 1/2] iommu/iova: Retry from last rb tree node if iova search fails Vijayanand Jitta
2020-11-17 23:24 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1e5b24a-512b-7279-8341-7f4495718ece@huawei.com \
--to=john.garry@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vinmenon@codeaurora.org \
--cc=vjitta@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®