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 BAABC4291E for ; Tue, 11 Apr 2023 20:03:04 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2846E40DFD; Tue, 11 Apr 2023 20:03:04 +0200 (CEST) Received: from mail-pj1-f49.google.com (mail-pj1-f49.google.com [209.85.216.49]) by mails.dpdk.org (Postfix) with ESMTP id D3FE440C35 for ; Tue, 11 Apr 2023 20:03:02 +0200 (CEST) Received: by mail-pj1-f49.google.com with SMTP id c3so9736030pjg.1 for ; Tue, 11 Apr 2023 11:03:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1681236182; x=1683828182; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=E7WoyhRbx50h2emMOGFkkx7FTvS8fO4MyIIUAYvGkf8=; b=09S9dZ32q1c/TJDUf1iJEQP6EQ2UTFqCXR8wkKg3AnaJt02GkN5Fk7heI5b82qCjlM b7LpU6pSxKcy+qQJOOQC25SzhfuAjWjZUcZmSEgWa1Km5r+lfCYXKqeVkJO+bQjk4VRB GcF16Rari79LRnEWzqOw35UPRG7RIQVA5adklpLqHXX2Qm0VlDb4fyGe0gNyXW4t9Y0R WmWeC6nTeO/R2OaJFR/s+JiR5dQ2SHiGBVECrSWzq/p9px26E1Yz+rtpNpjS5vyc0Ein hzoVAK9sl4lw0onEDoJgOITfae+ovEGYyIbt7t+0CiLH9iaWDNFsBTC2Nnp6Powbowzk lFlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681236182; x=1683828182; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=E7WoyhRbx50h2emMOGFkkx7FTvS8fO4MyIIUAYvGkf8=; b=6RROacq/AUXyWrrbIfiZ6hxbI6O5a60le5g4TOx/BTx6c8aehq8/XIWfdzQukqMiAF KaHZkFKM46WOcQa1Clhd1Z+7D2Mz2yp4Kv4NEzc/ffejNgF2vdJ5Tx7hS5lkaOZNrge+ AJDkx9zZe32bdOp3R2LKbGFcP8hEW3CuCm3QDv7bM/4m4c0CaRjw6Im+IgI2thkFh8VA FiGAz8qd8fVXOcin1Ar0JSkvAX0PDHrfUyZ5B/kMJeymg4L4rk/VxIC+YlVnfJNqp5ec guJTJEQUc/voP5HvouXfHR6WExf5dIBW9iYzbnVsc5G29YtohkP33476ylbI8lYwAwPi zgwQ== X-Gm-Message-State: AAQBX9fKnAuJvFvz7LuwBSmwxy408TT6fWJD8Q5XpEudBvi+b7Kzwmr+ lZZy8mC8YJ6r5WEkiABFNYnyYjmkng31fPKSBDNXE3B2 X-Google-Smtp-Source: AKy350b9s18J50LtL2gNpbKI+HPV6YIkKn194K3Mc5DydZ1283Tm2zu/md9W9HQlvp5Cf8wfq5kgNA== X-Received: by 2002:a17:90b:17cb:b0:23d:e0c1:8b8e with SMTP id me11-20020a17090b17cb00b0023de0c18b8emr5020274pjb.17.1681236181620; Tue, 11 Apr 2023 11:03:01 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id rj8-20020a17090b3e8800b0023b5566f744sm9558591pjb.39.2023.04.11.11.03.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Apr 2023 11:03:01 -0700 (PDT) Date: Tue, 11 Apr 2023 11:02:59 -0700 From: Stephen Hemminger To: Dinesh Kumar Cc: users@dpdk.org Subject: Re: How to use --vdev Options for ./dpdk-l3fwd? Message-ID: <20230411110259.5e1b40d6@hermes.local> In-Reply-To: References: <20230410160809.11e6747f@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On Tue, 11 Apr 2023 12:51:54 -0400 Dinesh Kumar wrote: > Hi Stephen , >=20 > 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 >=20 >=20 >=20 > *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* >=20 > 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 T= he > 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 >=20 >=20 >=20 > On Mon, Apr 10, 2023 at 7:08=E2=80=AFPM Stephen Hemminger < > stephen@networkplumber.org> wrote: =20 >=20 > > On Mon, 10 Apr 2023 18:47:59 -0400 > > Dinesh Kumar wrote: > > =20 > > > Hi There, > > > I am new to the DPDK example and having issue with using --vdev opti= ons > > > 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= =20 > > with =20 > > > --vdev =20 > > > > > > DPDK options are split into the options for the DPDK infrastructure (EA= L) > > 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 > > =20 I think you are assuming that the DPDK tap device is for using an existing tap device. That is not correct. The DPDK tap interface makes a tap device for its use.