From: Stephen Hemminger <stephen@networkplumber.org>
To: Dengdui Huang <huangdengdui@huawei.com>
Cc: <dev@dpdk.org>, <wathsala.vithanage@arm.com>,
<liuyonglong@huawei.com>, <fengchengwen@huawei.com>,
<haijie1@huawei.com>, <lihuisong@huawei.com>
Subject: Re: [PATCH] examples/l3fwd: optimize packet prefetch
Date: Wed, 25 Dec 2024 13:21:11 -0800 [thread overview]
Message-ID: <20241225132111.2efc1ab4@fedora> (raw)
In-Reply-To: <20241225075302.353013-1-huangdengdui@huawei.com>
On Wed, 25 Dec 2024 15:53:02 +0800
Dengdui Huang <huangdengdui@huawei.com> wrote:
> From: Dengdui Huang <huangdengdui@huawei.com>
> To: <dev@dpdk.org>
> CC: <wathsala.vithanage@arm.com>, <stephen@networkplumber.org>, <liuyonglong@huawei.com>, <fengchengwen@huawei.com>, <haijie1@huawei.com>, <lihuisong@huawei.com>
> Subject: [PATCH] examples/l3fwd: optimize packet prefetch
> Date: Wed, 25 Dec 2024 15:53:02 +0800
> X-Mailer: git-send-email 2.33.0
>
> The prefetch window depending on the hardware platform. The current prefetch
> policy may not be applicable to all platforms. In most cases, the number of
> packets received by Rx burst is small (64 is used in most performance reports).
> In L3fwd, the maximum value cannot exceed 512. Therefore, prefetching all
> packets before processing can achieve better performance.
>
> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
> ---
I think Vpp had a good description of how to unroll and deal with prefetch.
With larger burst sizes you don't want to prefetch the whole burst.
next prev parent reply other threads:[~2024-12-25 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 7:53 [PATCH] examples/l3fwd: optimize packet prefetch Dengdui Huang
2024-12-25 21:21 ` Stephen Hemminger [this message]
2025-01-08 13:42 ` Konstantin Ananyev
2025-01-09 11:31 ` huangdengdui
2025-01-10 9:37 ` [PATCH] examples/l3fwd: add option to set refetch offset Dengdui Huang
2025-01-10 17:19 ` Stephen Hemminger
2025-01-14 9:23 ` huangdengdui
2025-01-10 17:20 ` Stephen Hemminger
2025-01-14 9:22 ` huangdengdui
2025-01-14 16:07 ` Stephen Hemminger
2025-01-14 16:11 ` Stephen Hemminger
2025-02-19 16:44 ` Konstantin Ananyev
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=20241225132111.2efc1ab4@fedora \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=wathsala.vithanage@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.