[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25fdc11c-06b9-c16f-8427-77ac7673855c@linux.intel.com>
Date: Thu, 28 Apr 2022 08:16:27 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Robin Murphy <robin.murphy@....com>,
Tianyu Lan <ltykernel@...il.com>, m.szyprowski@...sung.com,
michael.h.kelley@...rosoft.com, kys@...rosoft.com,
parri.andrea@...il.com, thomas.lendacky@....com,
wei.liu@...nel.org, Tianyu Lan <Tianyu.Lan@...rosoft.com>,
linux-hyperv@...r.kernel.org, konrad.wilk@...cle.com,
linux-kernel@...r.kernel.org, kirill.shutemov@...el.com,
iommu@...ts.linux-foundation.org, andi.kleen@...el.com,
brijesh.singh@....com, vkuznets@...hat.com, hch@....de
Subject: Re: [RFC PATCH 1/2] swiotlb: Split up single swiotlb lock
On 4/28/2022 8:05 AM, Christoph Hellwig wrote:
> On Thu, Apr 28, 2022 at 07:55:39AM -0700, Andi Kleen wrote:
>> At least for TDX need parallelism with a single device for performance.
> So find a way to make it happen without exposing details to random
> drivers.
That's what the original patch (that this one is derived from) did.
It was completely transparent to everyone outside swiotlb.c
-Andi
Powered by blists - more mailing lists