From: Joerg Roedel <joro@8bytes.org>
To: iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
Arindam Nath <arindam.nath@amd.com>,
Joerg Roedel <joro@8bytes.org>
Subject: [PATCH 0/7] iommu/amd: Optimize iova queue flushing
Date: Wed, 7 Jun 2017 16:58:13 +0200 [thread overview]
Message-ID: <1496847500-6781-1-git-send-email-joro@8bytes.org> (raw)
Hi,
here is a patch-set to optimize the queue flushing in the
AMD IOMMU driver. It removes the global per-cpu flush queues
and implements queue-rings which are per-domain and per-cpu.
This allows some good optimizations to lower the flush-rate
of a domain and also lowers the contention on the queue
locks.
Regards,
Joerg
Joerg Roedel (7):
iommu/amd: Rip out old queue flushing code
iommu/amd: Add per-domain flush-queue data structures
iommu/amd: Make use of the per-domain flush queue
iommu/amd: Add locking to per-domain flush-queue
iommu/amd: Add flush counters to struct dma_ops_domain
iommu/amd: Add per-domain timer to flush per-cpu queues
iommu/amd: Remove queue_release() function
drivers/iommu/amd_iommu.c | 363 +++++++++++++++++++++++++++++-----------------
1 file changed, 227 insertions(+), 136 deletions(-)
--
2.7.4
next reply other threads:[~2017-06-07 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 14:58 Joerg Roedel [this message]
2017-06-07 14:58 ` [PATCH 1/7] iommu/amd: Rip out old queue flushing code Joerg Roedel
2017-06-07 14:58 ` [PATCH 2/7] iommu/amd: Add per-domain flush-queue data structures Joerg Roedel
2017-06-07 14:58 ` [PATCH 3/7] iommu/amd: Make use of the per-domain flush queue Joerg Roedel
2017-06-07 14:58 ` [PATCH 4/7] iommu/amd: Add locking to per-domain flush-queue Joerg Roedel
2017-06-07 14:58 ` [PATCH 5/7] iommu/amd: Add flush counters to struct dma_ops_domain Joerg Roedel
2017-06-07 14:58 ` [PATCH 6/7] iommu/amd: Add per-domain timer to flush per-cpu queues Joerg Roedel
2017-06-07 14:58 ` [PATCH 7/7] iommu/amd: Remove queue_release() function 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=1496847500-6781-1-git-send-email-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=arindam.nath@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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