All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Ankit Soni <Ankit.Soni@amd.com>
Cc: Rik van Riel <riel@surriel.com>,
	linux-kernel@vger.kernel.org,  kernel-team@meta.com,
	will@kernel.org, robin.murphy@arm.com, iommu@lists.linux.dev,
	 liam@infradead.org, maple-tree@lists.infradead.org,
	linux-mm@kvack.org,  ashok.raj@oss.qualcomm.com, jgg@ziepe.ca,
	kyle@mcmartin.ca
Subject: Re: [PATCH v5 0/3] iommu/iova: convert from rbtree to maple tree
Date: Fri, 9 Oct 2026 11:02:59 +0200	[thread overview]
Message-ID: <asith_7x71HNWMDl@8bytes.org> (raw)
In-Reply-To: <mcki6p5d6u7ofhiucoz6vi3jdldzmc7yv7n3ppoiwdjbwuriji@e2ezt37ga6i7>

Hi Ankit,

On Fri, Oct 09, 2026 at 08:45:29AM +0000, Ankit Soni wrote:
> Summary:
> 
> alloc_iova() is O(log n) in practice, on two CPUs and by two independent
> tools. The series costs about 2x on a near-empty tree and wins by orders
> of magnitude on a deep one, which is the trade you describe. Memory is
> the same within noise below 786k live IOVAs and a third less at 12.58M. 
> The costs are confined to microbenchmarks on near-empty trees, No regression
> in any real workload.

Thanks for providing these numbers, this is very helpful.

-Joerg


      reply	other threads:[~2026-10-09  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 15:25 [PATCH v5 0/3] iommu/iova: convert from rbtree to maple tree Rik van Riel
2026-08-18 15:25 ` [RFC PATCH 1/3] " Rik van Riel
2026-09-24 15:26   ` Robin Murphy
2026-10-05 14:54     ` Rik van Riel
2026-10-12 20:05     ` Rik van Riel
2026-08-18 15:25 ` [RFC PATCH 2/3] iommu/iova: defer maple tree erase on GFP_ATOMIC failure Rik van Riel
2026-08-18 15:25 ` [RFC PATCH 3/3] iommu/iova: add KUnit test suite Rik van Riel
2026-09-11 17:10 ` [PATCH v5 0/3] iommu/iova: convert from rbtree to maple tree Ashok Raj
2026-09-11 17:27   ` Rik van Riel
2026-09-11 18:26     ` Ashok Raj
2026-09-24 12:52 ` Jörg Rödel
2026-10-09  8:45   ` Ankit Soni
2026-10-09  9:02     ` Jörg Rödel [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=asith_7x71HNWMDl@8bytes.org \
    --to=joro@8bytes.org \
    --cc=Ankit.Soni@amd.com \
    --cc=ashok.raj@oss.qualcomm.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kernel-team@meta.com \
    --cc=kyle@mcmartin.ca \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=riel@surriel.com \
    --cc=robin.murphy@arm.com \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.