From: Rik van Riel <riel@surriel.com>
To: Ashok Raj <ashok.raj@oss.qualcomm.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
iommu@lists.linux.dev, liam@infradead.org,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
jgg@ziepe.ca, kyle@mcmartin.ca
Subject: Re: [PATCH v5 0/3] iommu/iova: convert from rbtree to maple tree
Date: Fri, 11 Sep 2026 13:27:29 -0400 [thread overview]
Message-ID: <d2f5889660e97f03fae2cd43ae32d8bf8edf3446.camel@surriel.com> (raw)
In-Reply-To: <aqQ2E68lmU3Fbjsk@hu-ashoraj-lv.qualcomm.com>
On Fri, 2026-09-11 at 10:10 -0700, Ashok Raj wrote:
> On Tue, Aug 18, 2026 at 11:25:00AM -0400, Rik van Riel wrote:
> > Occasionally production workloads at Meta run into the linear
> > search in
> > alloc_iova() in ways that cause real issues. For example, when
> > enough
> > CPUs at a time fall into the linear search trap, systems have been
> > known
> > to get stuck for so long that it causes soft lockups.
> >
>
> Something odd, except your cover letter rest of the patches are
> missing
> v5 prefix in your patch?
Ugh, indeed.
The content of the patches matches what I wanted
to send, though.
Do you want an identical v6-marked series, or
should I wait for feedback on the code?
kind regards,
Rik
--
All Rights Reversed.
next prev parent reply other threads:[~2026-09-11 17:28 UTC|newest]
Thread overview: 7+ 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-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 [this message]
2026-09-11 18:26 ` Ashok Raj
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=d2f5889660e97f03fae2cd43ae32d8bf8edf3446.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