mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rik van Riel <riel@surriel.com>
To: Robin Murphy <robin.murphy@arm.com>, linux-kernel@vger.kernel.org
Cc: kernel-team@meta.com, joro@8bytes.org, will@kernel.org,
	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: [RFC PATCH 1/3] iommu/iova: convert from rbtree to maple tree
Date: Mon, 12 Oct 2026 16:05:50 -0400	[thread overview]
Message-ID: <a27117bd826de3cb1e6c791e384d3291a040d8c6.camel@surriel.com> (raw)
In-Reply-To: <9547761f-7688-4351-b172-9e9d5fa28b15@arm.com>

On Thu, 2026-09-24 at 16:26 +0100, Robin Murphy wrote:
> 
> However, either way I do worry somewhat about the increase in 
> fragmentation and premature failures once the space starts to fill
> up. 

Now that we have AMD's test results, how do you
prefer we move forward with making the iova
allocation O(log n) ?

Do you want to pursue the maple tree approach,
and live with the fragmentation worry?

In that case, I'll apply your suggested cleanups.

Do you want me to code up an augmented rbtree
that propagates up (power of 2) aligned gap size,
so we can do an exact hole fit without having
to walk through the tree?

Do you have some other preference?

-- 
All Rights Reversed.

  parent reply	other threads:[~2026-10-12 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 15:25 [PATCH v5 0/3] " 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 [this message]
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

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=a27117bd826de3cb1e6c791e384d3291a040d8c6.camel@surriel.com \
    --to=riel@surriel.com \
    --cc=ashok.raj@oss.qualcomm.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --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=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 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®