From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4244E4291C for ; Tue, 11 Apr 2023 18:52:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3627D40DFD; Tue, 11 Apr 2023 18:52:07 +0200 (CEST) Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) by mails.dpdk.org (Postfix) with ESMTP id E89F140C35 for ; Tue, 11 Apr 2023 18:52:05 +0200 (CEST) Received: by mail-ua1-f42.google.com with SMTP id o2so6104697uao.11 for ; Tue, 11 Apr 2023 09:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=utexas-edu.20210112.gappssmtp.com; s=20210112; t=1681231925; x=1683823925; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2+TW+goB3OiKL54zflGaHnGtqBTkJJEZaB6H7W0QeVk=; b=AjjRpw4Rp1caWLFZx3s1wO0wwDe6OxKkGObESTiwP82GMpqQjBnELK2E27mKIwOKyn m5iC3OLx3Z1O61GJAiX48rXqoxGrJBUv/RNA5y7r9EFsPbDjahWaJoBw5kx1WwBzXCuj 4leUSdVI08Tzu01nUYhxWOM8UuBEwDbAMdeQ3LU/WH+Y/c3pN+tT7nVYqHjeJIcrwqZs dqnu6KNCR1HouifT9Ra20yqf3gTeEnvKXtGcjQPCvME6rEp4YyGaWVAnIvsFJsPsE+kc Xp0nJc31ahz3t2C/bW5Xy+KQuKFoE0aR+2I+BuII4U7gtuQQBtqN4s770pP38J3M0zOq R4Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681231925; x=1683823925; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2+TW+goB3OiKL54zflGaHnGtqBTkJJEZaB6H7W0QeVk=; b=EyYysQhxHzOB4MPlZLyFJxsGg1PytHqb6RLJCd75g/4zBkoGyMKDA2ZMB6jNUhjISu fhM4ZyaLSIzXjMf60Hlqt8bapEGRroRw/SUGuVy7ff+DLS9sJVE9AcUoQeyXqtfn9qB4 6qzkmqK9uZDC/IiF23i2FJXH9c+NFitiZXTPKfw50x6ZCKUsZQarrpa3hC4PJtLlVTod 9Vlp39MymTBYOqb4wxh+H1Vayx4CO+8c4Tk0A/dlyiIRMkpe7mt+JE2+nMZW0oAMNxJ9 cUV/klD5QkLoerMoDlHtQ16SxnhrzNIHAIB4uq0ph81kcWpVZKvhPTzgQRZuKaavxpF8 F8Ig== X-Gm-Message-State: AAQBX9fINvVHqQAvVMLxgPB4aS0whI8B30LgV/ZlLUKEIWfajOEWB8oI fnh5R88nalXYxJoqmuzl3TsobobeeHQlEuFHk3fs0QmyO3JEU8QhUbepOg== X-Google-Smtp-Source: AKy350YnyCYDvENst7PtdSVKsjfc44GliL5k9ztnEUnMdMzg4Umi1rnJTP6ImzAq2Ye81UotQRgqY6OFtef1UdBRqCQ= X-Received: by 2002:ab0:5549:0:b0:68a:7224:2034 with SMTP id u9-20020ab05549000000b0068a72242034mr8804276uaa.0.1681231925188; Tue, 11 Apr 2023 09:52:05 -0700 (PDT) MIME-Version: 1.0 References: <20230410160809.11e6747f@hermes.local> In-Reply-To: <20230410160809.11e6747f@hermes.local> From: Dinesh Kumar Date: Tue, 11 Apr 2023 12:51:54 -0400 Message-ID: Subject: Re: How to use --vdev Options for ./dpdk-l3fwd? To: stephen@networkplumber.org Cc: users@dpdk.org Content-Type: multipart/alternative; boundary="000000000000afb54605f9124ff0" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000afb54605f9124ff0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Stephen , Thanks for your suggestions.I am able to resolve --vdev error however I am having another issue related to buffer. .*/dpdk-l3fwd -c f -n 4 --vdev=3Dnet_tap3 -- -p 0x3 --config=3D"(0,0,1),(0,1,2)"* EAL: Detected CPU lcores: 8 EAL: Detected NUMA nodes: 1 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: No available 1048576 kB hugepages reported EAL: VFIO support initialized EAL: Probe PCI driver: net_virtio (1af4:1000) device: 0000:00:03.0 (socket 0) eth_virtio_pci_init(): Failed to init PCI device EAL: Requested device 0000:00:03.0 cannot be used EAL: Probe PCI driver: net_iavf (8086:154c) device: 0000:00:05.0 (socket 0) EAL: Probe PCI driver: net_iavf (8086:154c) device: 0000:00:06.0 (socket 0) TELEMETRY: No legacy callbacks, legacy socket not created Neither LPM, EM, or FIB selected, defaulting to LPM Initializing port 0 ... Creating queues: nb_rxq=3D2 nb_txq=3D4... Port 0 modified RSS hash function based on hardware support,requested:0xa38c configured:0x238c *iavf_dev_init_vlan(): Failed to update vlan offloadiavf_dev_configure(): configure VLAN failed: -95EAL: Error - exiting with code: 1 Cause: Cannot init mbuf pool on socket 0* Do I need to update any parameters? Do I need to add a routing rule parameter? Any help /pointers will be really appreciated. FYI. I just want to testL3 forwarding via DPDK using the Tap interface The flow is : On Vm1 .*/dpdk-l3fwd will create a Tap interface and then I will link this interface with a network namespace and then ping a destination address via the DPDK application running on VM1 and get captured on DPDK application running on another VM2 and I am stuck with creation Tap interface on VM1 via * . */dpdk-l3fwd.* Regards, Dinesh Kumar On Mon, Apr 10, 2023 at 7:08=E2=80=AFPM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Mon, 10 Apr 2023 18:47:59 -0400 > Dinesh Kumar wrote: > > > Hi There, > > I am new to the DPDK example and having issue with using --vdev option= s > > for DPDK example and it is throwing the below error. > > > > ./dpdk-l3fwd --log-level *:debug -c f -n 4 -- -p 0x3 --vdev > > 'net_pcap0,rx_pcap=3Dinput.pcap,tx_pcap=3Doutput.pcap' > > > > ----------------------- > > iavf_check_api_version(): Peer is supported PF host > > iavf_read_msg_from_pf(): Can't read msg from AQ > > iavf_read_msg_from_pf(): AQ from pf carries opcode 3, retval 0 > > iavf_dev_alarm_handler(): ICR01_ADMINQ is reported > > iavf_handle_pf_event_msg(): VIRTCHNL_EVENT_LINK_CHANGE event > > iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 26 > > EAL: lib.telemetry log level changed from disabled to debug > > TELEMETRY: Attempting socket bind to path > > '/var/run/dpdk/rte/dpdk_telemetry.v2' > > TELEMETRY: Socket creation and binding ok > > TELEMETRY: Telemetry initialized ok > > TELEMETRY: No legacy callbacks, legacy socket not created > > *./dpdk-l3fwd: unrecognized option '--vdev'* > > ./dpdk-l3fwd [EAL options] -- -p PORTMASK [-P] [--lookup] --config > > (port,queue,lcore)[,(port,queue,lcore)] [--rx-queue-size NPKTS] > > [--tx-queue-size NPKTS] [--eth-dest=3DX,MM:MM:MM:MM:MM:MM] [--max-pkt-l= en > > PKTLEN] [--no-numa] [--hash-entry-num] [--ipv6] [--parse-ptype] > > [--per-port-pool] [--mode] [--eventq-sched] [--event-vector > > [--event-vector-size SIZE] [--event-vector-tmo NS]] [-E] [-L] > > > > please let me know if I am missing some options that need to be added > with > > --vdev > > > DPDK options are split into the options for the DPDK infrastructure (EAL) > and those > used by the applications. They are separated by the -- option. > > In your example, the vdev option belongs to the DPDK infrastructure not > the application. > Put it it before the -- and it should work > --000000000000afb54605f9124ff0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Stephen ,

Thanks for your suggestions.I am able = to resolve --vdev error=C2=A0 however=C2=A0I am having another issue relate= d to buffer.
./dpdk-l3fwd -c f -n 4 --vdev=3Dnet_tap3 -- -p 0x3 --con= fig=3D"(0,0,1),(0,1,2)"
EAL: Detected CPU lcores: 8
EAL= : Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Mu= lti-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode &= #39;PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO= support initialized
EAL: Probe PCI driver: net_virtio (1af4:1000) devic= e: 0000:00:03.0 (socket 0)
eth_virtio_pci_init(): Failed to init PCI dev= ice
EAL: Requested device 0000:00:03.0 cannot be used
EAL: Probe PCI = driver: net_iavf (8086:154c) device: 0000:00:05.0 (socket 0)
EAL: Probe = PCI driver: net_iavf (8086:154c) device: 0000:00:06.0 (socket 0)
TELEMET= RY: No legacy callbacks, legacy socket not created
Neither LPM, EM, or F= IB selected, defaulting to LPM
Initializing port 0 ... Creating queues: = nb_rxq=3D2 nb_txq=3D4... Port 0 modified RSS hash function based on hardwar= e support,requested:0xa38c configured:0x238c
iavf_dev_init_vlan(): Fa= iled to update vlan offload
iavf_dev_configure(): configure VLAN failed:= -95
EAL: Error - exiting with code: 1
=C2=A0 Cause: Cannot init mbuf= pool on socket 0

Do I need to update any parameters?
Do I ne= ed to add a routing rule parameter?
Any help /pointers will be really ap= preciated.
FYI. I just want to testL3=C2=A0 forwarding via DPDK using th= e Tap interface The flow is :
On Vm1 ./dpdk-l3fwd will create a Tap i= nterface and then I will link this interface with a network namespace and t= hen ping a destination address via the DPDK application running on VM1 and = get captured on DPDK application running on another VM2 and I am stuck with= creation Tap interface on VM1 via=C2=A0 =C2=A0./dpdk-l3fwd.

Regards,
Dinesh Kumar



On Mon, Apr 10, 2023 at 7:08=E2=80=AFPM Stephen Hemminger <stephen@networkplumber.org> wrote= :
On Mon, 10 Apr= 2023 18:47:59 -0400
Dinesh Kumar <= raidinesh@utexas.edu> wrote:

> Hi There,
> I am new to the DPDK example and having issue with using=C2=A0 --vdev = options
> for DPDK example and it is throwing the below error.
>
> ./dpdk-l3fwd --log-level *:debug -c f -n 4 -- -p 0x3 --vdev
> 'net_pcap0,rx_pcap=3Dinput.pcap,tx_pcap=3Doutput.pcap'
>
> -----------------------
> iavf_check_api_version(): Peer is supported PF host
> iavf_read_msg_from_pf(): Can't read msg from AQ
> iavf_read_msg_from_pf(): AQ from pf carries opcode 3, retval 0
> iavf_dev_alarm_handler(): ICR01_ADMINQ is reported
> iavf_handle_pf_event_msg(): VIRTCHNL_EVENT_LINK_CHANGE event
> iavf_handle_virtchnl_msg(): adminq response is received, opcode =3D 26=
> EAL: lib.telemetry log level changed from disabled to debug
> TELEMETRY: Attempting socket bind to path
> '/var/run/dpdk/rte/dpdk_telemetry.v2'
> TELEMETRY: Socket creation and binding ok
> TELEMETRY: Telemetry initialized ok
> TELEMETRY: No legacy callbacks, legacy socket not created
> *./dpdk-l3fwd: unrecognized option '--vdev'*
> ./dpdk-l3fwd [EAL options] -- -p PORTMASK [-P] [--lookup] --config
> (port,queue,lcore)[,(port,queue,lcore)] [--rx-queue-size NPKTS]
> [--tx-queue-size NPKTS] [--eth-dest=3DX,MM:MM:MM:MM:MM:MM] [--max-pkt-= len
> PKTLEN] [--no-numa] [--hash-entry-num] [--ipv6] [--parse-ptype]
> [--per-port-pool] [--mode] [--eventq-sched] [--event-vector
> [--event-vector-size SIZE] [--event-vector-tmo NS]] [-E] [-L]
>
> please let me know if I am missing some options that need to be added = with
> --vdev


DPDK options are split into the options for the DPDK infrastructure (EAL) a= nd those
used by the applications. They are separated by the -- option.

In your example, the vdev option belongs to the DPDK infrastructure not the= application.
Put it it before the -- and it should work
--000000000000afb54605f9124ff0--