public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Huang Jiaqing <jiaqing.huang@intel.com>
Cc: baolu.lu@linux.intel.com, kvm@vger.kernel.org,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
	kevin.tian@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, 22 Aug 2023 15:32:26 +0800	[thread overview]
Message-ID: <fe03b53a-c9f9-cc6b-a1fd-d6fd2f1a1ddc@linux.intel.com> (raw)
In-Reply-To: <ZOOWMUmwG2jXOaXL@ziepe.ca>

On 2023/8/22 0:52, Jason Gunthorpe 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.
>>
>> To improve the performance of the IO page fault handler, replace
>> pci_get_domain_bus_and_slot() with a local red-black tree. A red-black
>> tree is a self-balancing binary search tree, which means that the
>> average time complexity of searching a red-black tree is O(log(n)). This
>> is significantly faster than O(n), so it can significantly improve the
>> performance of the IO page fault handler.
>>
>> In addition, we can only insert the affected devices (those that have IO
>> page fault enabled) into the red-black tree. This can further improve
>> the performance of the IO page fault handler.
>>
>> Signed-off-by: Huang Jiaqing<jiaqing.huang@intel.com>
>> ---
>>   drivers/iommu/intel/iommu.c | 68 +++++++++++++++++++++++++++++++++++++
>>   drivers/iommu/intel/iommu.h |  8 +++++
>>   drivers/iommu/intel/svm.c   | 13 +++----
>>   3 files changed, 81 insertions(+), 8 deletions(-)
> I feel like this should be a helper library provided by the core
> code, doesn't every PRI driver basically need the same thing?

It seems to be. pci_get_domain_bus_and_slot() is also used in the amd
driver. And the risc-v iommu driver under discussion is also proposing
this.

Best regards,
baolu

  reply	other threads:[~2023-08-22  7:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  7:16 [PATCH] iommu/vt-d: Introduce a rb_tree for looking up device Huang Jiaqing
2023-08-21 16:52 ` Jason Gunthorpe
2023-08-22  7:32   ` Baolu Lu [this message]
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

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=fe03b53a-c9f9-cc6b-a1fd-d6fd2f1a1ddc@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=jiaqing.huang@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