From: Cong Wang <xiyou.wangcong@gmail.com>
To: iommu@lists.linux-foundation.org
Cc: Robin Murphy <robin.murphy@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [Patch v3 0/3] iommu: reduce spinlock contention on fast path
Date: Mon, 20 Jan 2020 15:10:57 -0800 [thread overview]
Message-ID: <CAM_iQpWw9udHY5A2Gaq7+2WN__SEY2+U12D78=fiJ2xig1HJBA@mail.gmail.com> (raw)
In-Reply-To: <20191218043951.10534-1-xiyou.wangcong@gmail.com>
On Tue, Dec 17, 2019 at 8:40 PM Cong Wang <xiyou.wangcong@gmail.com> 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.
>
> (Resending v3 on Joerg's request.)
Hi, Joerg
Can you take these patches?
Thanks!
next prev parent reply other threads:[~2020-01-20 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 4:39 [Patch v3 0/3] iommu: reduce spinlock contention on fast path Cong Wang
2019-12-18 4:39 ` [Patch v3 1/3] iommu: avoid unnecessary magazine allocations Cong Wang
2020-01-21 11:11 ` Robin Murphy
2020-01-21 17:21 ` Cong Wang
2020-01-22 17:07 ` Robin Murphy
2020-01-22 17:54 ` Cong Wang
2019-12-18 4:39 ` [Patch v3 2/3] iommu: optimize iova_magazine_free_pfns() Cong Wang
2020-01-21 9:52 ` Robin Murphy
2020-01-21 17:29 ` Cong Wang
2020-01-22 17:34 ` Robin Murphy
2020-01-22 17:45 ` Cong Wang
2019-12-18 4:39 ` [Patch v3 3/3] iommu: avoid taking iova_rbtree_lock twice Cong Wang
2019-12-19 9:51 ` John Garry
2020-01-21 9:56 ` Robin Murphy
2020-03-03 11:33 ` John Garry
2020-01-20 23:10 ` Cong Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-06 21:38 [Patch v3 0/3] iommu: reduce spinlock contention on fast path Cong Wang
2019-12-06 21:57 ` Qian Cai
2019-12-10 14:53 ` John Garry
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='CAM_iQpWw9udHY5A2Gaq7+2WN__SEY2+U12D78=fiJ2xig1HJBA@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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).