DPDK patches and discussions
 help / color / mirror / Atom feed
From: "He, Guocai" <guocai.he.cn@windriver.com>
To: dev@dpdk.org
Subject: ethernet down with dpdk's "ipsec-secgw" with high traffic load testing
Date: Thu, 31 Oct 2024 15:48:57 +0800	[thread overview]
Message-ID: <5facf72f-1056-4c98-a1cc-d2cb8131555f@windriver.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1127 bytes --]

Hi all:

my dpdk version is 21.11

*1. Testing environment*

[WRL-LTS22/LS1043ARDB]             [Spirent/TestCenter]
<eth0:fm1-mac1>          <======>  UDP 512byte, 256pps traffic rate, Total 35Mbps
<eth1:fm1-mac2>  <---> for network capture
<eth2:fm1-mac3>  <---> NFS root
<eth3:fm1-mac4>  Not connected
<eth4:fm1-mac5>  Not connected
<eth5:fm1-mac6>  Not connected
<eth5:fm1-mac9>  Not connected

the attatched is the log.

2024-10-23
|-- debug
|   |-- ipsecgw-add-debug-log.patch       Add debug log for dpdk sample
|   `-- ls1043-secgw-debug.log            log file for ipsec-secgw
|-- fix
|   |-- example_modified_1018.patch       After applied this patch, it works good
|   `-- ls1043-secgw-modified.log         log for appled example_modified_1018.patch
`-- ipsecgw.cfg.1018                      ipsec-secgw config file


when testing, after sometime, the network is down, and use the fix patch 
of example_modified_1018.patch, it works well.

if anybody met the same issue or anybody know the root cause of the 
issue.  If the fix is reasonable and  no other issues will arise ?

Thanks very much


Guocai

[-- Attachment #1.2: Type: text/html, Size: 4156 bytes --]

[-- Attachment #2: 2024-10-23.tar.bz2 --]
[-- Type: application/x-bzip, Size: 238072 bytes --]

                 reply	other threads:[~2024-10-31  9:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5facf72f-1056-4c98-a1cc-d2cb8131555f@windriver.com \
    --to=guocai.he.cn@windriver.com \
    --cc=dev@dpdk.org \
    /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).