From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30060.outbound.protection.outlook.com [40.107.3.60]) by dpdk.org (Postfix) with ESMTP id 4C67D1BBFB for ; Fri, 11 Jan 2019 14:45:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+JOknnVWnFG7p10wFmFEiKrtSTH4UO8nNsQAH9+kl30=; b=V8oHZxOCy0pwvjxqEpVYgYxGT5a8ZRBiwNaKzOTF7G/DsLxBiyCadl0CKBzoM4S56L5FI2jZ4ry2RrvV6qGK5RFiQrqxfIZ/+hPeIxQlY4q8SH9bVxgiaPdPXr4kdwPKYl0IEdkR2DS1mxukoXWPotXiv/4er65DCbyk7ZjSpPA= Received: from VI1PR08MB3167.eurprd08.prod.outlook.com (52.133.15.142) by VI1PR08MB3263.eurprd08.prod.outlook.com (52.134.30.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1495.7; Fri, 11 Jan 2019 13:45:21 +0000 Received: from VI1PR08MB3167.eurprd08.prod.outlook.com ([fe80::8960:6756:4cdc:3954]) by VI1PR08MB3167.eurprd08.prod.outlook.com ([fe80::8960:6756:4cdc:3954%4]) with mapi id 15.20.1516.016; Fri, 11 Jan 2019 13:45:21 +0000 From: "Gavin Hu (Arm Technology China)" To: "users@dpdk.org" , "pierre.laurent@emutex.com" CC: Honnappa Nagarahalli , "Gavin Hu (Arm Technology China)" Thread-Topic: users Digest, Vol 168, Issue 3 Thread-Index: AQHUqDxGLSC8hj6XiUy+ZFeTFYzsxaWqDahQ Date: Fri, 11 Jan 2019 13:45:21 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Gavin.Hu@arm.com; x-originating-ip: [113.29.88.7] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR08MB3263; 6:VHFJBax+UVM825r9+GuM2zDv+ZFygNcErcFBwQtD8T1X3aTLfbcHd2N+ZGuyNQlU3ERlMZWEDRzcrG94iIYqpwiO4ds0MP5h3lTHxJYPrxHQmgf3whD0jPHZRPrfgHWW1ck+lQ0m1/lh6jNyEELMrQvAujPGcRFPqIlxVUC46OahSQV9mIr75wlv3JWn1iJ98p5Go+ZpjJRSGLsj1GDVdfBhalZTTgLUSbgPqDYAH60DpmB+V3QmEJQDdUZEWIcHV+4qujY4PFB4dV5MJEogzBQ/j3cFeUWjHBL3G9t3NLmxYmATDNX4Ugk4dYJJkJtHk3TavmTKeKn0RLPhiXyo1FCB0jHMZJt0gdZzxrr/5NBfkxhdHlHQZt1OgOynG+w3XEaBDpJWgL9RbY64diMRzW6ni+h4rk9DkFjTjNVYLt89dMv7WjJJD9X1u87LWos3+BkSz7nVnlVlL65xKT9goQ==; 5:4eCLUu2E3qHbDISK8PzgkyVWFlrQDl9uFXejqCCG0i6qbJc3wV6sKhENh9E/0Yrm/SGOWFMUQBSadS7TAFyAGbCPZIOwitEd8+AzGxvR7lQ703lOGVYaON8eZ1baw6Mfqb0q4MZ8EXffI/WIGTyhMEZ53+1zkW+lPIBf8DEkpGMUv2tLhuPkMkPqG7I2Pig367Q7YzGoKmUXPzBndUkayg==; 7:m2ewrRh9NX+55kdPBXRbLtylMOg5JJcWFmp2phmAl82rysz3WnxN03yMLwfi3NM7yvPdpo2JGfarNeziYuoB4vCWWB5FHgZxE2OMOcRQrwd5S/m+Jz1E71xIXltSixvSy9ifFzvrGb/uGF1HQrdI8w== x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR; x-ms-office365-filtering-correlation-id: 5430ae69-dc51-4f4c-2b40-08d677cb07f5 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:VI1PR08MB3263; x-ms-traffictypediagnostic: VI1PR08MB3263: x-microsoft-antispam-prvs: x-forefront-prvs: 09144DB0F7 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(39860400002)(396003)(346002)(136003)(40434004)(27574002)(13464003)(10533003)(18543002)(189003)(199004)(53946003)(4744004)(81166006)(86362001)(256004)(14444005)(6506007)(55236004)(3846002)(6116002)(53546011)(105586002)(106356001)(14454004)(186003)(25786009)(26005)(5024004)(102836004)(2906002)(5660300001)(6306002)(55016002)(7696005)(9686003)(76176011)(966005)(478600001)(45080400002)(72206003)(97736004)(11346002)(446003)(99286004)(486006)(2501003)(6246003)(33656002)(30864003)(316002)(8936002)(54906003)(110136005)(476003)(66066001)(4326008)(8676002)(229853002)(68736007)(305945005)(6436002)(7736002)(53936002)(74316002)(71200400001)(71190400001)(81156014)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR08MB3263; H:VI1PR08MB3167.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: DfhZLt00HC0HC/FgOs2FmA798g2b59HM1D8Tdy/x56TG0ZTei3GDDZaHW1VOvKQaipm8UHt0T9UI8lTgAawgV1qGswH1rhjGYCi+U42e64jhUoLwuZ4ZkuOpkl8Z1Ugx7kbo4nKJoJ59hRoLgO6KD/IGEzI6dIcotMJTl+sY/CMYT/tqDgi9Yvj9qrwZeZk6k7IocKzooeqpxi4mgMiBGnCMju5ZaXuB3u9ymIAFlVH6jSFlKSjk99qqKsL5TcpHQVXwRPSvpTUC7tG//matG7zBByiNdo0nMqDWZ1JvOghpvQlO6t04lNVhPMOhdpHYzhJDGrDSkvmoe1sTuJkCik6Nk/qTCfRJhKCrK62sl/kak2nJjQ54fIWkZ0dmOBdA2JVtwS9NDxgRVSt667Ic7XUSzg+lBC0v7EnWxVElD0s= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-Network-Message-Id: 5430ae69-dc51-4f4c-2b40-08d677cb07f5 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jan 2019 13:45:21.3006 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR08MB3263 Subject: Re: [dpdk-users] users Digest, Vol 168, Issue 3 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2019 13:45:23 -0000 > -----Original Message----- > From: users On Behalf Of users- > request@dpdk.org > Sent: Thursday, January 10, 2019 12:55 AM > To: users@dpdk.org > Subject: users Digest, Vol 168, Issue 3 > > Send users mailing list submissions to > users@dpdk.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mails.dpdk.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request@dpdk.org > > You can reach the person managing the list at > users-owner@dpdk.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. rte flow does not work on X550 - "Not supported by L2tunnel > filter" (Uiu Uioreanu) > 2. Re: HOW performance to run DPDK at ARM64 arch? (Pierre Laurent) > 3. DPDK procedure start Error: "PMD: Could not add multiqqdisc > (17): File exists" (hfli@netitest.com) > 4. mempool: creating pool out of an already allocatedmemory > (Pradeep Kumar Nalla) > 5. DPDK procedure start Error: "PMD: Could not add multiqqdisc > (17): File exists" (hfli@netitest.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 9 Jan 2019 16:36:23 +0200 > From: Uiu Uioreanu > To: users@dpdk.org > Subject: [dpdk-users] rte flow does not work on X550 - "Not supported > by L2tunnel filter" > Message-ID: > q_fpWhg@mail.gmail.com> > Content-Type: text/plain; charset=3D"UTF-8" > > Hi, > > I am trying to use rte flow on a X550 (ixgbe) and it does not work. > > For example, I used testpmd (sudo ./testpmd -c 0xf -n 1 -- -i) to > validate some simple flow rules: > - flow validate 0 ingress pattern eth / ipv4 / udp / end actions drop / e= nd > - flow validate 0 ingress pattern eth / ipv4 / udp / end actions end > - flow validate 0 ingress pattern eth / end actions drop end > - etc > > Every time, I receive "caught error type 9 (specific pattern item): > cause: 0x7ffddca42768, Not supported by L2 tunnel filter". > I also tried to make a sample application to use rte flow, but it also > gives the error 9 and the "Not supported by L2 tunnel filter" message. > > I don't understand what the problem is. Is the pattern from the flow > validate command wrong? Does the port need any additional > configuration? (except from binding a X550 NIC to > igb_uio/uio_pci_generic)? > > I am using DPDK 17.11. > > Thanks, > Uiu > > > ------------------------------ > > Message: 2 > Date: Thu, 27 Dec 2018 16:41:57 +0000 > From: Pierre Laurent > To: "users@dpdk.org" > Subject: Re: [dpdk-users] HOW performance to run DPDK at ARM64 arch? > Message-ID: <2736c618-8a28-a267-d05f-93021a3d5004@emutex.com> > Content-Type: text/plain; charset=3D"utf-8" > > Hi, > > Regarding your question 2, the TX+Rx numbers you get look strangely like > you are trying to use full duplex traffic on a PCIe x4 > > The real bandwidth needed by an interface is approximately ((pkt size + > 48) * pps) . > > 48 bytes is the approximate little overhead , per packet, for NIC > descriptors and PCIe overheads. This is an undocumented heuristic ...... > > I guess you are using the default DPDK options, the ethernet FCS is not i= n > PCIe bandwidth (stripped by the NIC on rx, generated by the NIC on TX). > Same for 20 bytes ethernet preamble. > > > If I assume you are using 60 bytes packets . ( 60 + 48 ) * (14 + 6) * 8= =3D > approx 17 Gbps =3D=3D more or less the bandwidth of a bidirectional x4 > interface. > > > Tools like "lspci" and "dmidecode" will help you to investigate the real > capabilities of the PCIe slots where your 82599 cards are plugged in. > > The output of dmidecode looks like the following example, and x2, x4, x8, > x16 indicate the number of lanes an interface will be able to use. The > more lanes, the fastest. > > System Slot Information > Designation: System Slot 1 > Type: x8 PCI Express > Current Usage: Available > Length: Long > ID: 1 > Characteristics: > 3.3 V is provided > > > To use a 82599 at full bidirectional rate, you need at least a x8 interfa= ce (1 > port) or x16 interface (2 ports) > > Regards, > > Pierre > > > On 27/12/2018 09:24, ????? wrote: > > recently, I have debug DPDK18.08 at my arm64 arch machine, with DPDK- > pktgen3.5.2. > but the performace is very low for bidirectional traffic with x86 machine > > here is my data: > hardware Conditions? > arm64: CPU - 64 cores, CPUfreq: 1.5GHz > MEM - 64 GiB > NIC - 82599ES dual port > x86: CPU - 4 cores, CPUfreq: 3.2GHz > MEM - 4GiB > NIC - 82599ES dual port > software Conditions: > system kernel: > arm64: linux-4.4.58 > x86: ubuntu16.04-4.4.0-generic > tools: > DPDK18.08, DPDK-pktgen3.5.2 > > test: > |----------| bi-directional |-------= ----| > | arm64 | port0 | < - > | port0 | x86 | > |----------| |= ----------| > > result > arm64 = x86 > Pkts/s (Rx/Tx) 10.2/6.0Mpps 6.0/14.80Mpp= s > MBits/s(Rx/Tx) 7000/3300 MBits/s 3300/9989 MBits/= s > > Questions? > 1?Why DPDK data performance would be so much worse than the x86 > architecture in arm64 addition? One reason is 1.5GHz vs. 3.2GHz, other possible reasons may include cpu aff= inity, crossing NUMA nodes? Hugepage sizes? Could you check these settings? > 2?above, Tx direction is not run full, Why Rx and TX affect each other? > > > > > > ------------------------------ > > Message: 3 > Date: Sun, 30 Dec 2018 20:18:46 +0800 > From: > To: , > Subject: [dpdk-users] DPDK procedure start Error: "PMD: Could not add > multiqqdisc (17): File exists" > Message-ID: <000a01d4a039$d0755f00$71601d00$@netitest.com> > Content-Type: text/plain;charset=3D"us-ascii" > > Hi Admin, > > > > Our DPDK procedure want to deploy on Hyper-v and Azure Cloud, so we > try it > on Hyper-v firstly. It need start 2 processes, a client process use port1= , a > server process use port2, port1 and port2 in one internal subnet on a > virtual switch, > > > > But only one process can be started successfully, the other said error, > "PMD: Could not add multiq qdisc (17): File exists", our procedure is > running well on Vmware/KVM/ASW, is there any help for this? > > > > Below is our env: > > > > OS: Windows 10 and Hyper-V on it > > Guest OS: CentOS7.6(Upgrade kernel to 4.20.0) > > DPDK version: 18.02.2 > > > > # uname -a > > Linux localhost.localdomain 4.20.0-1.el7.elrepo.x86_64 #1 SMP Sun Dec 23 > 20:11:51 EST 2018 x86_64 x86_64 x86_64 GNU/Linux > > > > root:/# ifconfig -a > > bond0: flags=3D5122 mtu 1500 > > ether 46:28:ec:c8:7a:74 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > lo: flags=3D73 mtu 65536 > > inet 127.0.0.1 netmask 255.0.0.0 > > inet6 ::1 prefixlen 128 scopeid 0x10 > > loop txqueuelen 1000 (Local Loopback) > > RX packets 75 bytes 6284 (6.1 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 75 bytes 6284 (6.1 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > mgmt1: flags=3D4163 mtu 1500 > > inet 192.168.16.130 netmask 255.255.255.0 broadcast 192.168.16.= 255 > > inet6 fe80::78e3:1af8:3333:ff45 prefixlen 64 scopeid 0x20 > > ether 00:15:5d:10:85:14 txqueuelen 1000 (Ethernet) > > RX packets 5494 bytes 706042 (689.4 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 2163 bytes 438205 (427.9 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > mgmt2: flags=3D4163 mtu 1500 > > ether 00:15:5d:10:85:15 txqueuelen 1000 (Ethernet) > > RX packets 3131 bytes 518243 (506.0 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > port1: flags=3D4675 mtu > 1500 > > ether 00:15:5d:10:85:16 txqueuelen 1000 (Ethernet) > > RX packets 1707 bytes 163778 (159.9 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 693 bytes 70666 (69.0 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > port2: flags=3D4675 mtu > 1500 > > ether 00:15:5d:10:85:17 txqueuelen 1000 (Ethernet) > > RX packets 900 bytes 112256 (109.6 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 1504 bytes 122428 (119.5 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > root:/# ethtool -i port1 > > driver: hv_netvsc > > version: > > firmware-version: N/A > > expansion-rom-version: > > bus-info: > > supports-statistics: yes > > supports-test: no > > supports-eeprom-access: no > > supports-register-dump: no > > supports-priv-flags: no > > root:/# ethtool -i port2 > > driver: hv_netvsc > > version: > > firmware-version: N/A > > expansion-rom-version: > > bus-info: > > supports-statistics: yes > > supports-test: no > > supports-eeprom-access: no > > supports-register-dump: no > > supports-priv-flags: no > > root:/# > > > > Start server process successfully > > # ./Tester -l 3 -n 4 --vdev=3D"net_vdev_netvsc1,iface=3Dport2" --socket-m= em > 1500 > --file-prefix server > > EAL: Detected 4 lcore(s) > > EAL: No free hugepages reported in hugepages-1048576kB > > EAL: Multi-process socket /var/log/.server_unix > > EAL: Probing VFIO support... > > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using > unreliable > clock cycles ! > > PMD: net_failsafe: Initializing Fail-safe PMD for > net_failsafe_net_vdev_netvsc1_id0 > > PMD: net_failsafe: Creating fail-safe device on NUMA socket 0 > > PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc1_id0 as dtap0 > > PMD: net_failsafe: MAC address is 00:15:5d:10:85:17 > > > > Concorrently start client process failed > > # ./Tester -l 2 -n 4 --vdev=3D"net_vdev_netvsc0,iface=3Dport1" --socket-m= em > 1500 > --file-prefix client > > EAL: Detected 4 lcore(s) > > EAL: No free hugepages reported in hugepages-1048576kB > > EAL: Multi-process socket /var/log/.client_unix > > EAL: Probing VFIO support... > > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using > unreliable > clock cycles ! > > PMD: net_failsafe: Initializing Fail-safe PMD for > net_failsafe_net_vdev_netvsc0_id0 > > PMD: net_failsafe: Creating fail-safe device on NUMA socket 0 > > PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc0_id0 as dtap0 > > PMD: Could not add multiq qdisc (17): File exists > > PMD: dtap0: failed to create multiq qdisc. > > PMD: Disabling rte flow support: File exists(17) > > PMD: Remote feature requires flow support. > > PMD: TAP Unable to initialize net_tap_net_vdev_netvsc0_id0 > > EAL: Driver cannot attach the device (net_tap_net_vdev_netvsc0_id0) > > PMD: net_failsafe: sub_device 1 probe failed (No such file or directory) > > PMD: net_failsafe: MAC address is 06:5f:a6:0a:b4:f9 > > vdev_probe(): failed to initialize : PMD: net_failsafe: MAC address is > 06:5f:a6:0a:b4:f9 > > device > > EAL: Bus (vdev) probe failed. > > > > > > > > Thanks and Regards, > > Jack > > > > ------------------------------ > > Message: 4 > Date: Wed, 2 Jan 2019 11:29:52 +0000 > From: Pradeep Kumar Nalla > To: "users@dpdk.org" > Subject: [dpdk-users] mempool: creating pool out of an already > allocatedmemory > Message-ID: > 5.namprd18.prod.outlook.com> > > Content-Type: text/plain; charset=3D"us-ascii" > > Hello > > Is there a way or API to create a mempool out of already allocated > memory? > > Thanks > Pradeep. > > > ------------------------------ > > Message: 5 > Date: Fri, 4 Jan 2019 11:46:48 +0800 > From: > To: > Cc: , > Subject: [dpdk-users] DPDK procedure start Error: "PMD: Could not add > multiqqdisc (17): File exists" > Message-ID: <000f01d4a3e0$1f6bb060$5e431120$@netitest.com> > Content-Type: text/plain;charset=3D"us-ascii" > > Hi Matan, > > > > Could you help us for below error? > > > > PMD: Could not add multiq qdisc (17): File exists > > PMD: dtap0: failed to create multiq qdisc. > > PMD: Disabling rte flow support: File exists(17) > > PMD: Remote feature requires flow support. > > PMD: TAP Unable to initialize net_tap_net_vdev_netvsc0_id0 > > EAL: Driver cannot attach the device (net_tap_net_vdev_netvsc0_id0) > > PMD: net_failsafe: sub_device 1 probe failed (No such file or directory) > > PMD: net_failsafe: MAC address is 06:5f:a6:0a:b4:f9 > > vdev_probe(): failed to initialize : PMD: net_failsafe: MAC address is > 06:5f:a6:0a:b4:f9 > > device > > EAL: Bus (vdev) probe failed. > > > > > > Our DPDK procedure want to deploy on Hyper-v and Azure Cloud, so we > try it > on Hyper-v firstly. It need start 2 processes, a client process use port1= , a > server process use port2, port1 and port2 in one internal subnet on a > virtual switch, > > > > But only one process can be started successfully, the other said error, > "PMD: Could not add multiq qdisc (17): File exists", our procedure is > running well on Vmware/KVM/ASW, is there any help for this? > > > > Below is our env: > > > > OS: Windows 10 and Hyper-V on it > > Guest OS: CentOS7.6(Upgrade kernel to 4.20.0) > > DPDK version: 18.02.2 > > > > # uname -a > > Linux localhost.localdomain 4.20.0-1.el7.elrepo.x86_64 #1 SMP Sun Dec 23 > 20:11:51 EST 2018 x86_64 x86_64 x86_64 GNU/Linux > > > > root:/# ifconfig -a > > bond0: flags=3D5122 mtu 1500 > > ether 46:28:ec:c8:7a:74 txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > lo: flags=3D73 mtu 65536 > > inet 127.0.0.1 netmask 255.0.0.0 > > inet6 ::1 prefixlen 128 scopeid 0x10 > > loop txqueuelen 1000 (Local Loopback) > > RX packets 75 bytes 6284 (6.1 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 75 bytes 6284 (6.1 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > mgmt1: flags=3D4163 mtu 1500 > > inet 192.168.16.130 netmask 255.255.255.0 broadcast 192.168.16.= 255 > > inet6 fe80::78e3:1af8:3333:ff45 prefixlen 64 scopeid 0x20 > > ether 00:15:5d:10:85:14 txqueuelen 1000 (Ethernet) > > RX packets 5494 bytes 706042 (689.4 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 2163 bytes 438205 (427.9 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > mgmt2: flags=3D4163 mtu 1500 > > ether 00:15:5d:10:85:15 txqueuelen 1000 (Ethernet) > > RX packets 3131 bytes 518243 (506.0 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > port1: flags=3D4675 mtu > 1500 > > ether 00:15:5d:10:85:16 txqueuelen 1000 (Ethernet) > > RX packets 1707 bytes 163778 (159.9 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 693 bytes 70666 (69.0 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > port2: flags=3D4675 mtu > 1500 > > ether 00:15:5d:10:85:17 txqueuelen 1000 (Ethernet) > > RX packets 900 bytes 112256 (109.6 KiB) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 1504 bytes 122428 (119.5 KiB) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > root:/# ethtool -i port1 > > driver: hv_netvsc > > version: > > firmware-version: N/A > > expansion-rom-version: > > bus-info: > > supports-statistics: yes > > supports-test: no > > supports-eeprom-access: no > > supports-register-dump: no > > supports-priv-flags: no > > root:/# ethtool -i port2 > > driver: hv_netvsc > > version: > > firmware-version: N/A > > expansion-rom-version: > > bus-info: > > supports-statistics: yes > > supports-test: no > > supports-eeprom-access: no > > supports-register-dump: no > > supports-priv-flags: no > > root:/# > > > > Start server process successfully > > # ./VM_DPDK -l 3 -n 4 --vdev=3D"net_vdev_netvsc1,iface=3Dport2" --socket-= mem > 1500 --file-prefix server > > EAL: Detected 4 lcore(s) > > EAL: No free hugepages reported in hugepages-1048576kB > > EAL: Multi-process socket /var/log/.server_unix > > EAL: Probing VFIO support... > > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using > unreliable > clock cycles ! > > PMD: net_failsafe: Initializing Fail-safe PMD for > net_failsafe_net_vdev_netvsc1_id0 > > PMD: net_failsafe: Creating fail-safe device on NUMA socket 0 > > PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc1_id0 as dtap0 > > PMD: net_failsafe: MAC address is 00:15:5d:10:85:17 > > > > Concorrently start client process failed > > # ./VM_DPDK -l 2 -n 4 --vdev=3D"net_vdev_netvsc0,iface=3Dport1" --socket-= mem > 1500 --file-prefix client > > EAL: Detected 4 lcore(s) > > EAL: No free hugepages reported in hugepages-1048576kB > > EAL: Multi-process socket /var/log/.client_unix > > EAL: Probing VFIO support... > > EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using > unreliable > clock cycles ! > > PMD: net_failsafe: Initializing Fail-safe PMD for > net_failsafe_net_vdev_netvsc0_id0 > > PMD: net_failsafe: Creating fail-safe device on NUMA socket 0 > > PMD: Initializing pmd_tap for net_tap_net_vdev_netvsc0_id0 as dtap0 > > PMD: Could not add multiq qdisc (17): File exists > > PMD: dtap0: failed to create multiq qdisc. > > PMD: Disabling rte flow support: File exists(17) > > PMD: Remote feature requires flow support. > > PMD: TAP Unable to initialize net_tap_net_vdev_netvsc0_id0 > > EAL: Driver cannot attach the device (net_tap_net_vdev_netvsc0_id0) > > PMD: net_failsafe: sub_device 1 probe failed (No such file or directory) > > PMD: net_failsafe: MAC address is 06:5f:a6:0a:b4:f9 > > vdev_probe(): failed to initialize : PMD: net_failsafe: MAC address is > 06:5f:a6:0a:b4:f9 > > device > > EAL: Bus (vdev) probe failed. > > > > > > > > Thanks and Regards, > > Jack > > > > End of users Digest, Vol 168, Issue 3 > ************************************* IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you.