From: Will Deacon <will@kernel.org>
To: "vjitta@codeaurora.org" <vjitta@codeaurora.org>,
joro@8bytes.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
robin.murphy@arm.com, vinmenon@codeaurora.org
Subject: Re: [PATCH v5 1/2] iommu/iova: Retry from last rb tree node if iova search fails
Date: Tue, 17 Nov 2020 23:24:29 +0000 [thread overview]
Message-ID: <160565419447.2778079.10643367410535150698.b4-ty@kernel.org> (raw)
In-Reply-To: <1601451864-5956-1-git-send-email-vjitta@codeaurora.org>
On Wed, 30 Sep 2020 13:14:23 +0530, vjitta@codeaurora.org wrote:
> When ever a new iova alloc request comes iova is always searched
> from the cached node and the nodes which are previous to cached
> node. So, even if there is free iova space available in the nodes
> which are next to the cached node iova allocation can still fail
> because of this approach.
>
> Consider the following sequence of iova alloc and frees on
> 1GB of iova space
>
> [...]
Applied to arm64 (for-next/iommu/iova), thanks!
[1/2] iommu/iova: Retry from last rb tree node if iova search fails
https://git.kernel.org/arm64/c/4e89dce72521
[2/2] iommu/iova: Free global iova rcache on iova alloc failure
https://git.kernel.org/arm64/c/6fa3525b455a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2020-11-17 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:44 vjitta
2020-09-30 7:44 ` [PATCH v5 2/2] iommu/iova: Free global iova rcache on iova alloc failure vjitta
2020-10-20 9:18 ` Vijayanand Jitta
2020-11-03 12:35 ` Robin Murphy
2020-11-03 14:31 ` John Garry
2020-11-03 15:59 ` Robin Murphy
2020-11-09 11:12 ` John Garry
2020-10-20 9:17 ` [PATCH v5 1/2] iommu/iova: Retry from last rb tree node if iova search fails Vijayanand Jitta
2020-11-17 23:24 ` Will Deacon [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=160565419447.2778079.10643367410535150698.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vinmenon@codeaurora.org \
--cc=vjitta@codeaurora.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®