[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJwJo6YmF+tW2_it2BLCP6fLBrUR6kfx7jG0hsNy6uYG203Jfw@mail.gmail.com>
Date: Thu, 3 Dec 2020 06:04:25 +0000
From: Dmitry Safonov <0x7f454c46@...il.com>
To: Will Deacon <will@...nel.org>
Cc: John Garry <john.garry@...wei.com>, Joerg Roedel <joro@...tes.org>,
robin.murphy@....com, Catalin Marinas <catalin.marinas@....com>,
kernel-team@...roid.com, xiyou.wangcong@...il.com,
linuxarm@...wei.com, iommu@...ts.linux-foundation.org,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH v3 0/4] iommu/iova: Solve longterm IOVA issue
On Tue, 1 Dec 2020 at 21:50, Will Deacon <will@...nel.org> wrote:
>
> On Tue, 17 Nov 2020 18:25:30 +0800, John Garry wrote:
> > This series contains a patch to solve the longterm IOVA issue which
> > leizhen originally tried to address at [0].
> >
> > A sieved kernel log is at the following, showing periodic dumps of IOVA
> > sizes, per CPU and per depot bin, per IOVA size granule:
> > https://raw.githubusercontent.com/hisilicon/kernel-dev/topic-iommu-5.10-iova-debug-v3/aging_test
> >
> > [...]
>
> Applied the final patch to arm64 (for-next/iommu/iova), thanks!
>
> [4/4] iommu: avoid taking iova_rbtree_lock twice
> https://git.kernel.org/arm64/c/3a651b3a27a1
Glad it made in next, 2 years ago I couldn't convince iommu maintainer
it's worth it (but with a different justification):
https://lore.kernel.org/linux-iommu/20180621180823.805-3-dima@arista.com/
Thanks,
Dmitry
Powered by blists - more mailing lists