From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id CB354A0093;
	Tue,  3 May 2022 11:34:07 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 705A940C35;
	Tue,  3 May 2022 11:34:07 +0200 (CEST)
Received: from mail-io1-f51.google.com (mail-io1-f51.google.com
 [209.85.166.51]) by mails.dpdk.org (Postfix) with ESMTP id 252AA40691
 for <dev@dpdk.org>; Tue,  3 May 2022 11:34:06 +0200 (CEST)
Received: by mail-io1-f51.google.com with SMTP id g21so18357743iom.13
 for <dev@dpdk.org>; Tue, 03 May 2022 02:34:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:from:date:message-id:subject:to;
 bh=kg27rUt0IaKGsHD0h6+GFHsZWT2+NqKeITlufyAFYfs=;
 b=nPW43o/as71Iq9baEygn1CzQBRNbvjsY5Yb+r8V59KHcxd0Mn/RY1VO0Mm0zwtR2Nx
 ysauz4LiWA+w6schIg9h93kD3PC18ngAvklUz0u2CCst0i+9KR97dbAZSQlk4poQttBR
 KmZe6IFT6miVJs5whKCe3NeVsYGsuzMTkj6G5GiDWzE1YkLyV9c5dT62zp6hGi0hCNSK
 jhNxGsEcnJnXfQdgkRS8xcQwo8jFmwX1RR1ZiKddtauyhxEPSL4m7JoVRjSPMqETH6KV
 U1ZAGwabSSloz8TpQoJrZYVmfDq2LY2vkekEoclOdZSQOL8kYXSlTcCPm6r7zwA/lcSi
 bDew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=kg27rUt0IaKGsHD0h6+GFHsZWT2+NqKeITlufyAFYfs=;
 b=cnCaN00CmKrUgOe74SDdS4HqF9xTJ45+sSSy9+zgdu1bk3DNnF0ouH+3o8KtMBRfHm
 vcVqQHQLl6wO9LfZOl6Lim+vsTIZjt844hscVTaYDuw5ybpNb/kSjW7e1Z53EcBZynbt
 ZbDIERiDBF1EYsV+QU5l+u2LTslVClvDgbj4zkf9Kqxtf96cZ0ew9TQJuMvw9CdwTOHl
 esBf68AawwRIIimJLptPKAfFbTFu+q29enYw9dqUFgpbGc9aSl474ZD6O3x7qTCdsPJ8
 DjTBtds5c34jSYanFdlaQW8GcQ69ySQkVVDAfdg/3A4Xhl28BcM/hsaNNq47TB8JEQRL
 urSA==
X-Gm-Message-State: AOAM5314WRCyI3IbJsS9K7W0ggO4WsLQh5XRJNVmzqimRZrYJRe0KhwI
 IyVGckiuoCKpxNKBwOQt7oMnBHPEaonP9bjesWm7ufb8WwA=
X-Google-Smtp-Source: ABdhPJxO6uOO1V3SpznkwyCO0SEIZgvCSxkl4uqS0C2t2wgZq7Bb7uij+6wVAiZh1Nst7lgwanqtlTubhd2B8KVM6K0=
X-Received: by 2002:a05:6638:1927:b0:32b:7441:1341 with SMTP id
 p39-20020a056638192700b0032b74411341mr2575209jal.181.1651570444620; Tue, 03
 May 2022 02:34:04 -0700 (PDT)
MIME-Version: 1.0
From: Maxime Ramiara <max1mo.ram8@gmail.com>
Date: Tue, 3 May 2022 11:33:53 +0200
Message-ID: <CABhX6Bv9K4yuguoGAQjHvueOq7y=H+D4d2VCC9BV7xYRYAuU4A@mail.gmail.com>
Subject: Softnic test failed + questions
To: dev@dpdk.org
Content-Type: multipart/alternative; boundary="000000000000ac574e05de183544"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

--000000000000ac574e05de183544
Content-Type: text/plain; charset="UTF-8"

Hi all,

I'm a beginner with dpdk. With my team, we developed a dpdk app with the
following pipeline:

NIC RX -> RX Thread -> Worker Thread -> TX Thread -> NIC TX.

Within the RX Thread, we parse some headers. Within the worker thread,
we're using the hierarchical scheduler. To sum up, we want to replace the
HS with the traffic manager.
However, it seems the TM can only be set up on a NIC. This is not what we
want because we're doing some packet processing stuff within the TX Thread.


Thus, we thought about the SoftNIC as a solution for our problem. Would it
be possible to develop a pipeline like this ?

NIC RX -> RX Thread -> SoftNIC with TM -> Worker Thread -> TX Thread -> NIC
TX.

It looks like the "firmware.cli" script and the packet framework offer us
some freedom to make our pipeline.
First and foremost, I tried to test the SoftNIC with the following command
in the doc :

./testpmd -c 0x3 --vdev 'net_softnic0,firmware=<script
path>/firmware.cli,cpu_id=0,conn_port=8086' -- -i
     --forward-mode=softnic --portmask=0x2

Below are my network devices with the command log:

./usertools/dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:19:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
unused=i40e
0000:19:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
unused=i40e

Network devices using kernel driver
===================================
0000:01:00.0 'I350 Gigabit Network Connection 1521' if=eno3 drv=igb
unused=vfio-pci *Active*

Other Network devices
=====================
0000:01:00.1 'I350 Gigabit Network Connection 1521' unused=igb,vfio-pci

Then, the command log of test-pmd:

sudo ./dpdk-testpmd --vdev
'net_softnic0,firmware=./firmware.cli,cpu_id=0,conn_port=8087' -- -i
--forward-mode=softnic --portmask=0x2
[sudo] password for user:
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
EAL: Using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_i40e (8086:1572) device: 0000:19:00.0 (socket 0)
EAL: Probe PCI driver: net_i40e (8086:1572) device: 0000:19:00.1 (socket 0)
TELEMETRY: No legacy callbacks, legacy socket not created
Interactive-mode selected
Invalid softnic packet forwarding mode
previous number of forwarding ports 3 - changed to number of configured
ports 1
testpmd: create a new mbuf pool <mb_pool_0>: n=395456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mb_pool_1>: n=395456, size=2176, socket=1
testpmd: preferred mempool ops selected: ring_mp_mc

Warning! port-topology=paired and odd forward ports number, the last port
will pair with itself.

Configuring Port 0 (socket 0)
Port 0: E4:43:4B:04:D1:4E
Configuring Port 1 (socket 0)
Port 1: E4:43:4B:04:D1:50
Configuring Port 2 (socket 0)
; SPDX-License-Identifier: BSD-3-Clause
; Copyright(c) 2018 Intel Corporation

link LINK0 dev 0000:19:00.0

pipeline RX period 10 offset_port_id 0
pipeline RX port in bsz 32 link LINK0 rxq 0
pipeline RX port out bsz 32 swq RXQ0
pipeline RX table match stub
pipeline RX port in 0 table 0
pipeline RX table 0 rule add match default action fwd port 0

pipeline TX period 10 offset_port_id 0
pipeline TX port in bsz 32 swq TXQ0
pipeline TX port out bsz 32 link LINK0 txq 0
pipeline TX table match stub
pipeline TX port in 0 table 0
pipeline TX table 0 rule add match default action fwd port 0

thread 1 pipeline RX enable
Command "thread pipeline enable" failed.
thread 1 pipeline TX enable
Command "thread pipeline enable" failed.
Port 2: 00:00:00:00:00:00
Checking link statuses...
Done
testpmd>
Port 0: link state change event

Port 1: link state change event


Can anyone please help us on this ?

Regards,

Max.

--000000000000ac574e05de183544
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br><br>I&#39;m a beginner with dpdk. With my team,=
 we developed a dpdk app with the following pipeline:<br><br>NIC RX -&gt; R=
X Thread -&gt; Worker Thread -&gt; TX Thread -&gt; NIC TX.<br><br>Within th=
e RX Thread, we parse some headers. Within the worker thread, we&#39;re usi=
ng the hierarchical scheduler. To sum up, we want to replace the HS with th=
e traffic manager.<br>However, it seems the TM can only be set up on a NIC.=
 This is not what we want because we&#39;re doing some packet processing st=
uff within the TX Thread.<br><br><br>Thus, we thought about the SoftNIC as =
a solution for our problem. Would it be possible to develop a pipeline like=
 this ?<br><br>NIC RX -&gt; RX Thread -&gt; SoftNIC with TM -&gt; Worker Th=
read -&gt; TX Thread -&gt; NIC TX.<br><br>It looks like the &quot;firmware.=
cli&quot; script and the packet framework offer us some freedom to make our=
 pipeline. <br>First and foremost, I tried to test the SoftNIC with the fol=
lowing command in the doc : <br><br>./testpmd -c 0x3 --vdev &#39;net_softni=
c0,firmware=3D&lt;script path&gt;/firmware.cli,cpu_id=3D0,conn_port=3D8086&=
#39; -- -i<br>=C2=A0 =C2=A0 =C2=A0--forward-mode=3Dsoftnic --portmask=3D0x2=
<br><br>Below are my network devices with the command log: <br><br>./userto=
ols/dpdk-devbind.py --status<br><br>Network devices using DPDK-compatible d=
river<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>0000:=
19:00.0 &#39;Ethernet Controller X710 for 10GbE SFP+ 1572&#39; drv=3Dvfio-p=
ci unused=3Di40e<br>0000:19:00.1 &#39;Ethernet Controller X710 for 10GbE SF=
P+ 1572&#39; drv=3Dvfio-pci unused=3Di40e<br><br>Network devices using kern=
el driver<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>0000:01:00.0 &#39;I350 Gig=
abit Network Connection 1521&#39; if=3Deno3 drv=3Digb unused=3Dvfio-pci *Ac=
tive*<br><br>Other Network devices<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>0000:01:00.1 &#39;I350 Gigabit Network Conne=
ction 1521&#39; unused=3Digb,vfio-pci<br><br>Then, the command log of test-=
pmd: <br><br>sudo ./dpdk-testpmd --vdev &#39;net_softnic0,firmware=3D./firm=
ware.cli,cpu_id=3D0,conn_port=3D8087&#39; -- -i --forward-mode=3Dsoftnic --=
portmask=3D0x2<br>[sudo] password for user: <br>EAL: Detected CPU lcores: 3=
2<br>EAL: Detected NUMA nodes: 2<br>EAL: Detected static linkage of DPDK<br=
>EAL: Multi-process socket /var/run/dpdk/rte/mp_socket<br>EAL: Selected IOV=
A mode &#39;PA&#39;<br>EAL: VFIO support initialized<br>EAL: Using IOMMU ty=
pe 8 (No-IOMMU)<br>EAL: Probe PCI driver: net_i40e (8086:1572) device: 0000=
:19:00.0 (socket 0)<br>EAL: Probe PCI driver: net_i40e (8086:1572) device: =
0000:19:00.1 (socket 0)<br>TELEMETRY: No legacy callbacks, legacy socket no=
t created<br>Interactive-mode selected<br>Invalid softnic packet forwarding=
 mode<br>previous number of forwarding ports 3 - changed to number of confi=
gured ports 1<br>testpmd: create a new mbuf pool &lt;mb_pool_0&gt;: n=3D395=
456, size=3D2176, socket=3D0<br>testpmd: preferred mempool ops selected: ri=
ng_mp_mc<br>testpmd: create a new mbuf pool &lt;mb_pool_1&gt;: n=3D395456, =
size=3D2176, socket=3D1<br>testpmd: preferred mempool ops selected: ring_mp=
_mc<br><br>Warning! port-topology=3Dpaired and odd forward ports number, th=
e last port will pair with itself.<br><br>Configuring Port 0 (socket 0)<br>=
Port 0: E4:43:4B:04:D1:4E<br>Configuring Port 1 (socket 0)<br>Port 1: E4:43=
:4B:04:D1:50<br>Configuring Port 2 (socket 0)<br>; SPDX-License-Identifier:=
 BSD-3-Clause<br>; Copyright(c) 2018 Intel Corporation<br><br>link LINK0 de=
v 0000:19:00.0<br><br>pipeline RX period 10 offset_port_id 0<br>pipeline RX=
 port in bsz 32 link LINK0 rxq 0<br>pipeline RX port out bsz 32 swq RXQ0<br=
>pipeline RX table match stub<br>pipeline RX port in 0 table 0<br>pipeline =
RX table 0 rule add match default action fwd port 0<br><br>pipeline TX peri=
od 10 offset_port_id 0<br>pipeline TX port in bsz 32 swq TXQ0<br>pipeline T=
X port out bsz 32 link LINK0 txq 0<br>pipeline TX table match stub<br>pipel=
ine TX port in 0 table 0<br>pipeline TX table 0 rule add match default acti=
on fwd port 0<br><br>thread 1 pipeline RX enable<br>Command &quot;thread pi=
peline enable&quot; failed.<br>thread 1 pipeline TX enable<br>Command &quot=
;thread pipeline enable&quot; failed.<br>Port 2: 00:00:00:00:00:00<br>Check=
ing link statuses...<br>Done<br>testpmd&gt; <br>Port 0: link state change e=
vent<br><br>Port 1: link state change event<br><br><br>Can anyone please he=
lp us on this ?<br><br>Regards,<br><br>Max.<br></div>

--000000000000ac574e05de183544--