From: Joerg Roedel <joro@8bytes.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [Patch v2 0/3] iommu: reduce spinlock contention on fast path
Date: Tue, 17 Dec 2019 10:43:04 +0100 [thread overview]
Message-ID: <20191217094304.GF8689@8bytes.org> (raw)
In-Reply-To: <20191129004855.18506-1-xiyou.wangcong@gmail.com>
On Thu, Nov 28, 2019 at 04:48:52PM -0800, Cong Wang wrote:
> This patchset contains three small optimizations for the global spinlock
> contention in IOVA cache. Our memcache perf test shows this reduced its
> p999 latency down by 45% on AMD when IOMMU is enabled.
Sounds nice. Can you please re-send with Robin Murphy on Cc? Robin, can
you have a look at these IOVA changes please?
Thanks,
Joerg
next prev parent reply other threads:[~2019-12-17 9:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 0:48 [Patch v2 0/3] iommu: reduce spinlock contention on fast path Cong Wang
2019-11-29 0:48 ` [Patch v2 1/3] iommu: match the original algorithm Cong Wang
2019-11-29 14:43 ` John Garry
2019-11-30 5:58 ` Cong Wang
2019-12-02 10:55 ` John Garry
2019-12-03 19:26 ` Cong Wang
2019-12-02 16:58 ` Christoph Hellwig
2019-12-03 19:24 ` Cong Wang
2019-11-29 0:48 ` [Patch v2 2/3] iommu: optimize iova_magazine_free_pfns() Cong Wang
2019-11-29 13:24 ` John Garry
2019-11-30 6:02 ` Cong Wang
2019-12-02 10:02 ` John Garry
2019-12-03 19:40 ` Cong Wang
2019-12-02 16:59 ` Christoph Hellwig
2019-12-03 19:28 ` Cong Wang
2019-11-29 0:48 ` [Patch v2 3/3] iommu: avoid taking iova_rbtree_lock twice Cong Wang
2019-11-29 13:34 ` John Garry
2019-11-30 6:03 ` Cong Wang
2019-12-17 9:43 ` Joerg Roedel [this message]
2019-12-18 4:32 ` [Patch v2 0/3] iommu: reduce spinlock contention on fast path Cong Wang
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=20191217094304.GF8689@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).