From: Robin Murphy <robin.murphy@arm.com>
To: joro@8bytes.org
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Misc IOVA tweaks
Date: Tue, 19 Sep 2017 14:48:38 +0100 [thread overview]
Message-ID: <cover.1505827369.git.robin.murphy@arm.com> (raw)
While I was elbow-deep in the IOVA code, a few other things came to
light which don't really fit into the rbtree optimisation series.
Patches #1 and #2 are more or less just cleanup, while patch #3
complements Tomasz' recent PCI allocation patch as it aims to
potentially improve the same situation.
Last time I checked, these should all apply independently and without
major conflicts against any other in-flight IOVA patches.
Robin.
Robin Murphy (3):
iommu/iova: Simplify domain destruction
iommu/iova: Make rcache limit_pfn handling more robust
iommu/iova: Try harder to allocate from rcache magazine
drivers/iommu/iova.c | 73 ++++++++++++++++++++--------------------------------
1 file changed, 28 insertions(+), 45 deletions(-)
--
2.13.4.dirty
next reply other threads:[~2017-09-19 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 13:48 Robin Murphy [this message]
[not found] ` <cover.1505827369.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-09-19 13:48 ` [PATCH 1/3] iommu/iova: Simplify domain destruction Robin Murphy
2017-09-19 13:48 ` Robin Murphy
2017-09-19 13:48 ` [PATCH 2/3] iommu/iova: Make rcache limit_pfn handling more robust Robin Murphy
2017-09-19 13:48 ` [PATCH 3/3] iommu/iova: Try harder to allocate from rcache magazine Robin Murphy
[not found] ` <8127fabc219811d8169189e9d7177d42bc74bcbf.1505827369.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-09-27 14:00 ` Joerg Roedel
2017-09-27 14:00 ` Joerg Roedel
[not found] ` <20170927140051.GO8398-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-09-27 16:50 ` Robin Murphy
2017-09-27 16:50 ` Robin Murphy
2017-09-28 10:31 ` [PATCH v2] " Robin Murphy
2017-09-28 13:41 ` Joerg Roedel
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=cover.1505827369.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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.