From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
Tianyu Lan <ltykernel@gmail.com>,
m.szyprowski@samsung.com, michael.h.kelley@microsoft.com,
kys@microsoft.com, parri.andrea@gmail.com,
thomas.lendacky@amd.com, wei.liu@kernel.org,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
linux-hyperv@vger.kernel.org, konrad.wilk@oracle.com,
linux-kernel@vger.kernel.org, kirill.shutemov@intel.com,
iommu@lists.linux-foundation.org, andi.kleen@intel.com,
brijesh.singh@amd.com, vkuznets@redhat.com, hch@lst.de
Subject: Re: [RFC PATCH 1/2] swiotlb: Split up single swiotlb lock
Date: Thu, 28 Apr 2022 08:05:10 -0700 [thread overview]
Message-ID: <YmqtJr5lxDruT/9s@infradead.org> (raw)
In-Reply-To: <1517d2f0-08d6-a532-7810-2161b2dff421@linux.intel.com>
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.
next prev parent reply other threads:[~2022-04-28 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:14 [RFC PATCH 0/2] swiotlb: Introduce swiotlb device allocation function Tianyu Lan
2022-04-28 14:14 ` [RFC PATCH 1/2] swiotlb: Split up single swiotlb lock Tianyu Lan
2022-04-28 14:44 ` Robin Murphy
2022-04-28 14:45 ` Christoph Hellwig
2022-04-28 14:55 ` Andi Kleen
2022-04-28 15:05 ` Christoph Hellwig [this message]
2022-04-28 15:16 ` Andi Kleen
2022-04-28 15:07 ` Robin Murphy
2022-04-28 16:02 ` Andi Kleen
2022-04-28 16:59 ` Robin Murphy
2022-04-28 14:56 ` Robin Murphy
2022-04-28 15:54 ` Tianyu Lan
2022-04-29 14:21 ` [RFC PATCH] swiotlb: Add Child IO TLB mem support Tianyu Lan
2022-04-29 14:25 ` Tianyu Lan
2022-04-28 14:14 ` [RFC PATCH 2/2] Swiotlb: Add device bounce buffer allocation interface Tianyu Lan
2022-04-28 15:50 ` Tianyu Lan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YmqtJr5lxDruT/9s@infradead.org \
--to=hch@infradead.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=ak@linux.intel.com \
--cc=andi.kleen@intel.com \
--cc=brijesh.singh@amd.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kirill.shutemov@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltykernel@gmail.com \
--cc=m.szyprowski@samsung.com \
--cc=michael.h.kelley@microsoft.com \
--cc=parri.andrea@gmail.com \
--cc=robin.murphy@arm.com \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).