From: "wangjie (L)" <wangjie125@huawei.com>
To: Peng Zhang <zhangpeng.00@bytedance.com>, <joro@8bytes.org>,
<will@kernel.org>
Cc: <iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<robin.murphy@arm.com>, <haifeng.zhao@linux.intel.com>,
<john.garry@huawei.com>
Subject: Re: [PATCH v2] iommu/iova: Optimize alloc_iova with rbtree_augmented
Date: Wed, 21 Sep 2022 18:54:01 +0800 [thread overview]
Message-ID: <36ce6959-a4ed-bf33-9e7c-f35a63bf9434@huawei.com> (raw)
In-Reply-To: <bdcf9676-7846-1f14-1dd1-80cb9dcb0794@bytedance.com>
Tested-by: Jie Wang <wangjie125@huawei.com>
On 2022/9/21 11:55, Peng Zhang wrote:
>> This patch seems to solve the performance issues i have. Currently my
>> nic's rx performance is unstable in large-capacity scenarios. I
>> applied this patch to 5.19 rc4 and tested 8 times rx performance in
>> these scenes. Here are test results, "before" row is the result of
>> 5.19 rc4. "after" row means 5.19 rc4 with this patch, the unit is Mbits/s
>>
>> 1 2 3 4 5 6 7 8
>> before 55430 76701 84194 77560 88292 90106
>> 87770 77273
>> after 92770 92767 92792 92764 92742 92696
>> 92781 92756
>>
>> Obviously, after using this patch, the performance is stable.
>
> Thank you for your test. Can you add a "Tested-by" token?
> I plan to update the commit message in the next version.
> .
>
prev parent reply other threads:[~2022-09-21 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 9:51 Peng Zhang
2022-08-24 12:30 ` Ethan Zhao
2022-08-25 8:10 ` [External] " Peng Zhang
2022-08-26 8:58 ` Ethan Zhao
2022-08-26 10:28 ` Peng Zhang
2022-09-01 10:45 ` John Garry
2022-09-02 3:30 ` Peng Zhang
2022-09-21 1:15 ` wangjie (L)
2022-09-21 3:55 ` Peng Zhang
2022-09-21 10:54 ` wangjie (L) [this message]
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=36ce6959-a4ed-bf33-9e7c-f35a63bf9434@huawei.com \
--to=wangjie125@huawei.com \
--cc=haifeng.zhao@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=john.garry@huawei.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=zhangpeng.00@bytedance.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
all inboxes | Powered by JetHome®