From: Stephen Hemminger <stephen@networkplumber.org>
To: fengchengwen <fengchengwen@huawei.com>
Cc: thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: add one example of DPI ?
Date: Mon, 28 Apr 2025 08:49:01 -0700 [thread overview]
Message-ID: <20250428084901.0aeeee04@hermes.local> (raw)
In-Reply-To: <2c503191-c235-4fbc-ae7a-d21dbe83d2a7@huawei.com>
On Mon, 28 Apr 2025 16:20:22 +0800
fengchengwen <fengchengwen@huawei.com> wrote:
> Hi all,
>
> Currently, we supported several DPI application scenarios performance tuning,
> in these scenarios, the DPDK library ethdev, ring, mbuf and hash APIs are used.
>
> One of the scenarios is:
>
> ------------------------ -------------------------
> | | rte_ring-0 | |
> | packet-recv-process | ===> rte_ring-1 ===> | packet-detect-process |
> | | ... | |
> | | rte_ring-n | |
> ------------------------ -------------------------
>
> packet-recv-process dispatch flow to different rings by such 'rte_hash_crc' function.
> packet-detect-process build flow context based on rte_hash library.
>
> I think it is necessary to add a DPI example to show that DPDK has the basic
> capability of building DPI applications and provides best performance practices.
>
> Hope to listen to the community's opinions.
>
> Thanks
>
Did you consider the impact of CPU cache on this scenario.
When you process the packet in two different threads, it ends up adding
an additional data cache miss which can cut performance in half.
next prev parent reply other threads:[~2025-04-28 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 8:20 fengchengwen
2025-04-28 15:49 ` Stephen Hemminger [this message]
2025-04-29 1:14 ` fengchengwen
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=20250428084901.0aeeee04@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=thomas@monjalon.net \
/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).