[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220627153150.106995-1-ltykernel@gmail.com>
Date: Mon, 27 Jun 2022 11:31:48 -0400
From: Tianyu Lan <ltykernel@...il.com>
To: corbet@....net, rafael@...nel.org, len.brown@...el.com,
pavel@....cz, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
hch@...radead.org, m.szyprowski@...sung.com, robin.murphy@....com,
paulmck@...nel.org, akpm@...ux-foundation.org,
keescook@...omium.org, songmuchun@...edance.com,
rdunlap@...radead.org, damien.lemoal@...nsource.wdc.com,
michael.h.kelley@...rosoft.com, kys@...rosoft.com
Cc: Tianyu Lan <Tianyu.Lan@...rosoft.com>,
iommu@...ts.linux-foundation.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
vkuznets@...hat.com, wei.liu@...nel.org, parri.andrea@...il.com,
thomas.lendacky@....com, linux-hyperv@...r.kernel.org,
kirill.shutemov@...el.com, andi.kleen@...el.com
Subject: [PATCH 0/2] swiotlb: Split up single swiotlb lock
From: Tianyu Lan <Tianyu.Lan@...rosoft.com>
Traditionally swiotlb was not performance critical because it was only
used for slow devices. But in some setups, like TDX/SEV confidential
guests, all IO has to go through swiotlb. Currently swiotlb only has a
single lock. Under high IO load with multiple CPUs this can lead to
significat lock contention on the swiotlb lock.
Patch 1 is to introduce swiotlb area concept and split up single swiotlb
lock.
Patch 2 set swiotlb area number with lapic number
Tianyu Lan (2):
swiotlb: Split up single swiotlb lock
x86/ACPI: Set swiotlb area according to the number of lapic entry in
MADT
.../admin-guide/kernel-parameters.txt | 4 +-
arch/x86/kernel/acpi/boot.c | 3 +
include/linux/swiotlb.h | 27 +++
kernel/dma/swiotlb.c | 202 ++++++++++++++----
4 files changed, 197 insertions(+), 39 deletions(-)
--
2.25.1
Powered by blists - more mailing lists