From: Ashok Raj <ashok.raj@oss.qualcomm.com>
To: Rik van Riel <riel@surriel.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
robin.murphy@arm.com, joro@8bytes.org, will@kernel.org,
iommu@lists.linux.dev, jgg@ziepe.ca, kyle@mcmartin.ca,
"ashok.raj@oss.qualcomm.com" <ashok.raj@oss.qualcomm.com>
Subject: Re: [PATCH 0/3] convert iova to maple tree
Date: Thu, 25 Jun 2026 11:30:44 -0700 [thread overview]
Message-ID: <aj1z1Go5TfC75oAz@hu-ashoraj-lv.qualcomm.com> (raw)
In-Reply-To: <20260624030853.2340880-1-riel@surriel.com>
On Tue, Jun 23, 2026 at 11:07:33PM -0400, Rik van Riel wrote:
> Based on 5d6919055dec Linux 7.1-rc3
>
> v4:
> - reduce the size of struct iova to 16 bytes
> - simplify the (hopefully rare) remove_iova GFP_ATOMIC failure path
> - test case for the deferred free code
Somehow the v4 in the subject got dropped out.
> v3:
> - switch to maple tree (suggested by Robin Murphy)
> v2:
> - clean up selftests (thanks Jason Gunthorpe)
> - address Sashiko concerns
> - drop the search-with-alignment, since most iova requests
> should be of similar sizes, so the worst case behavior
> is unlikely to hit once ranges are excluded by the augmented
> rbtree
>
>
--
/ashok.raj
ashok.raj@oss.qualcomm.com
Qualcomm Inc
prev parent reply other threads:[~2026-06-25 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 3:07 Rik van Riel
2026-06-24 3:07 ` [PATCH 1/3] iova: convert from rbtree " Rik van Riel
2026-06-24 3:07 ` [PATCH 2/3] iova: add KUnit test suite Rik van Riel
2026-06-24 3:07 ` [PATCH 3/3] iova: defer maple tree erase on GFP_ATOMIC failure Rik van Riel
2026-06-25 15:51 ` Ashok Raj
2026-06-26 18:32 ` Rik van Riel
2026-06-25 18:30 ` Ashok Raj [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=aj1z1Go5TfC75oAz@hu-ashoraj-lv.qualcomm.com \
--to=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=linux-kernel@vger.kernel.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 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®