From: Cong Wang <xiyou.wangcong@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: iommu@lists.linux-foundation.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v3 2/3] iommu: optimize iova_magazine_free_pfns()
Date: Wed, 22 Jan 2020 09:45:25 -0800 [thread overview]
Message-ID: <CAM_iQpWM52sPfwWQPqZ-Fd_w8MgnN14WOK5gJAi3JCg1AwQGCw@mail.gmail.com> (raw)
In-Reply-To: <e8789016-858a-b354-aa98-637e1d453fc3@arm.com>
On Wed, Jan 22, 2020 at 9:34 AM Robin Murphy <robin.murphy@arm.com> wrote:
> Sorry, but without convincing evidence, this change just looks like
> churn for the sake of it.
The time I wasted on arguing with you isn't worth anything than
the value this patch brings. So let's just drop it to save some
time.
Thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-01-22 17:45 UTC|newest]
Thread overview: 17+ 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 [this message]
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 ` [Patch v3 0/3] iommu: reduce spinlock contention on fast path Cong Wang
-- strict thread matches above, loose matches on Subject: below --
2019-12-06 21:38 Cong Wang
2019-12-06 21:38 ` [Patch v3 2/3] iommu: optimize iova_magazine_free_pfns() 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=CAM_iQpWM52sPfwWQPqZ-Fd_w8MgnN14WOK5gJAi3JCg1AwQGCw@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=iommu@lists.linux-foundation.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).