From: "Huang, Jiaqing" <jiaqing.huang@intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: kvm@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, will@kernel.org,
robin.murphy@arm.com, kevin.tian@intel.com,
baolu.lu@linux.intel.com, jacob.jun.pan@linux.intel.com,
yi.l.liu@intel.com, yi.y.sun@intel.com
Subject: Re: [PATCH] iommu/vt-d: Introduce a rb_tree for looking up device
Date: Tue, 26 Sep 2023 16:25:26 +0800 [thread overview]
Message-ID: <56cc2e4e-81dd-f2d2-f690-6d82217b9e7d@intel.com> (raw)
In-Reply-To: <ZRFA3uj1-QjlXpGx@8bytes.org>
On 9/25/2023 4:12 PM, Joerg Roedel wrote:
> On Mon, Aug 21, 2023 at 12:16:59AM -0700, Huang Jiaqing wrote:
>> The existing IO page fault handler locates the PCI device by calling
>> pci_get_domain_bus_and_slot(), which searches the list of all PCI
>> devices until the desired PCI device is found. This is inefficient
>> because the algorithm efficiency of searching a list is O(n). In the
>> critical path of handling an IO page fault, this can cause a significant
>> performance bottleneck.
> Can you elaborate a little more on the 'significant performance
> bottleneck' part? Where do you see this as a problem?
>
> Regards,
>
> Joerg
While lots of dsa devices were enabled, parallel dsa_test with large
transfer size
would be executed ineffciently and cause cpu stuck in
pci_get_domain_bus_and_slot
by lock competition. The introduced patch could significantly improve
the speed and
prevent the CPU from getting sutck. It maybe confusing for "significant
performance
bottleneck" since it didn't benefit all the cases, would rephase it in
the new patch. Thanks!
BRs,
Jiaqing
prev parent reply other threads:[~2023-09-26 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 7:16 Huang Jiaqing
2023-08-21 16:52 ` Jason Gunthorpe
2023-08-22 7:32 ` Baolu Lu
2023-08-23 1:47 ` kernel test robot
2023-08-23 10:19 ` kernel test robot
2023-09-25 8:12 ` Joerg Roedel
2023-09-26 8:25 ` Huang, Jiaqing [this message]
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=56cc2e4e-81dd-f2d2-f690-6d82217b9e7d@intel.com \
--to=jiaqing.huang@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.com \
/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
all inboxes | Powered by JetHome®