[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230711025452.35475-1-zhangzekun11@huawei.com>
Date: Tue, 11 Jul 2023 10:54:50 +0800
From: Zhang Zekun <zhangzekun11@...wei.com>
To: <robin.murphy@....com>, <joro@...tes.org>, <will@...nel.org>,
<iommu@...ts.linux.dev>, <linux-kernel@...r.kernel.org>
CC: <guohanjun@...wei.com>, <xuqiang36@...wei.com>,
<chenweilong@...wei.com>, <thunder.leizhen@...wei.com>,
<zhangzekun11@...wei.com>
Subject: [PATCH -next 0/2] iommu/iova: optimize the iova rcache
The struct of iova rcache has diffcult in dealing with machine with
lots of cpus, because every cpu has a cpu_rcache and they need to
exchange iova in a fixed length buffer rcache->depot, this buffer
can sometimes become a bottle neck of allocating iova from iova_rcache.
The number of iova_cpu_rcache can grow with the number of cpus in
iova_rcache, but the size of rcache->depot will not. The deeper of
rcache->depot can help iova_rcache cache more iovas, and can help
iova_rcache better dealing with senarios in which drivers allocating
and free iovas on different cpu cores. We only let the size of rcache->depot
to grow with the number of cpus which is larger than 32 to avoid potential
performance decrease on machines which don't have much cpus.
Also, it is unsafe to directly free cpu rcache magazines in free_iova_rcaches,
add check before freeing it.
Zhang Zekun (2):
iommu/iova: Add check for cpu_rcache in free_iova_rcaches
iommu/iova: allocate iova_rcache->depot dynamicly
drivers/iommu/iova.c | 36 +++++++++++++++++++++++++++++++-----
1 file changed, 31 insertions(+), 5 deletions(-)
--
2.17.1
Powered by blists - more mailing lists