[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220301115340.GA3077@lst.de>
Date: Tue, 1 Mar 2022 12:53:40 +0100
From: Christoph Hellwig <hch@....de>
To: Tianyu Lan <ltykernel@...il.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, m.szyprowski@...sung.com,
robin.murphy@....com, michael.h.kelley@...rosoft.com,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
iommu@...ts.linux-foundation.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, vkuznets@...hat.com,
brijesh.singh@....com, konrad.wilk@...cle.com,
parri.andrea@...il.com, thomas.lendacky@....com,
"krish.sadhukhan@...cle.com" <krish.sadhukhan@...cle.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH V2 1/2] Swiotlb: Add swiotlb_alloc_from_low_pages switch
On Fri, Feb 25, 2022 at 10:28:54PM +0800, Tianyu Lan wrote:
> One more perspective is that one device may have multiple queues and
> each queues should have independent swiotlb bounce buffer to avoid spin
> lock overhead. The number of queues is only available in the device
> driver. This means new API needs to be called in the device driver
> according to queue number.
Well, given how hell bent people are on bounce buffering we might
need some scalability work there anyway.
Powered by blists - more mailing lists