From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: will.deacon-5wv7dgnIgG8@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: [PATCH 0/3] SMMUv3 CMD_SYNC optimisation
Date: Fri, 18 Aug 2017 18:33:01 +0100 [thread overview]
Message-ID: <cover.1503075486.git.robin.murphy@arm.com> (raw)
Hi all,
Waiting for the command queue to drain for CMD_SYNC completion is likely
a contention hotspot on high-core-count systems. If the SMMU is coherent
and supports MSIs, though, we can use this cool feature (as suggested by
the architecture, no less) to make syncs effectively non-blocking for
anyone other than the caller.
I don't have any hardware that supports MSIs, but this has at least
passed muster on the Fast Model with cache modelling enabled - I'm hoping
the Qualcomm machines have the appropriate configuration to actually test
how well it works in reality. If it is worthwhile, I do have most of a
plan for how we can do something similar in the non-MSI polling case (it's
mostly a problem of handling the queue-wrapping edge cases correctly).
Robin.
Robin Murphy (3):
iommu/arm-smmu-v3: Specialise CMD_SYNC handling
iommu/arm-smmu-v3: Forget about cmdq-sync interrupt
iommu/arm-smmu-v3: Utilise CMD_SYNC MSI feature
drivers/iommu/arm-smmu-v3.c | 117 +++++++++++++++++++++++++++++---------------
1 file changed, 77 insertions(+), 40 deletions(-)
--
2.13.4.dirty
WARNING: multiple messages have this Message-ID (diff)
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] SMMUv3 CMD_SYNC optimisation
Date: Fri, 18 Aug 2017 18:33:01 +0100 [thread overview]
Message-ID: <cover.1503075486.git.robin.murphy@arm.com> (raw)
Hi all,
Waiting for the command queue to drain for CMD_SYNC completion is likely
a contention hotspot on high-core-count systems. If the SMMU is coherent
and supports MSIs, though, we can use this cool feature (as suggested by
the architecture, no less) to make syncs effectively non-blocking for
anyone other than the caller.
I don't have any hardware that supports MSIs, but this has at least
passed muster on the Fast Model with cache modelling enabled - I'm hoping
the Qualcomm machines have the appropriate configuration to actually test
how well it works in reality. If it is worthwhile, I do have most of a
plan for how we can do something similar in the non-MSI polling case (it's
mostly a problem of handling the queue-wrapping edge cases correctly).
Robin.
Robin Murphy (3):
iommu/arm-smmu-v3: Specialise CMD_SYNC handling
iommu/arm-smmu-v3: Forget about cmdq-sync interrupt
iommu/arm-smmu-v3: Utilise CMD_SYNC MSI feature
drivers/iommu/arm-smmu-v3.c | 117 +++++++++++++++++++++++++++++---------------
1 file changed, 77 insertions(+), 40 deletions(-)
--
2.13.4.dirty
next reply other threads:[~2017-08-18 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 17:33 Robin Murphy [this message]
2017-08-18 17:33 ` [PATCH 0/3] SMMUv3 CMD_SYNC optimisation Robin Murphy
[not found] ` <cover.1503075486.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-08-18 17:33 ` [PATCH 1/3] iommu/arm-smmu-v3: Specialise CMD_SYNC handling Robin Murphy
2017-08-18 17:33 ` Robin Murphy
2017-08-18 17:33 ` [PATCH 2/3] iommu/arm-smmu-v3: Forget about cmdq-sync interrupt Robin Murphy
2017-08-18 17:33 ` Robin Murphy
2017-08-18 17:33 ` [PATCH 3/3] iommu/arm-smmu-v3: Utilise CMD_SYNC MSI feature Robin Murphy
2017-08-18 17:33 ` Robin Murphy
2017-08-25 4:44 ` [PATCH 0/3] SMMUv3 CMD_SYNC optimisation Nate Watterson
2017-08-25 4:44 ` Nate Watterson
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.1503075486.git.robin.murphy@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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.