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 60B9F42913 for ; Tue, 11 Apr 2023 01:08:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EF65540DFD; Tue, 11 Apr 2023 01:08:13 +0200 (CEST) Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com [209.85.214.179]) by mails.dpdk.org (Postfix) with ESMTP id BD0C840C35 for ; Tue, 11 Apr 2023 01:08:12 +0200 (CEST) Received: by mail-pl1-f179.google.com with SMTP id d9443c01a7336-1a52eca0bedso3519235ad.2 for ; Mon, 10 Apr 2023 16:08:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1681168091; x=1683760091; 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=f2UQAcCg6TPqtZdbySC+2rd1LFY5/KVRtTKopC1skPc=; b=sbUYr74ZG4oYZkSxu4FCT0axDF9zJ6KzSntJ7Jm4jQuDxQRN6L2nfDm4TDxrsjbhJV 0wICZ1CKbGD1DZomp6a3kxpiewnV3C8m3e10BJuL/S7LlQLs30eq53tKCW1Az9qwuIFm qKbqAL8dSw9BI6IADwqy/VcRMQw8UF7U2R28TXgJ9FUDNRIw1PAmTmBnymeQm/jj+JGG DxX+m02V5YsRGD6wlIM0E2Igcgo74SdHpees9fPcEioIXXGVLJaqio7osmDNBwB4QSyi QXGVerJ8FxwzofkV9+d3J1quQzS5yk//4eBcSGP8IdSbDJRLCgdTzANyswgMkb457lgy wjtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681168091; x=1683760091; 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=f2UQAcCg6TPqtZdbySC+2rd1LFY5/KVRtTKopC1skPc=; b=ruuZw4deRhvb9dkRW+XcT2LD+zmHMFLMcuNfxYLWHlVvrk0Yb+MMxaf0+BQk4wnnib 8OV7aQwGSn9u4243BIHyv78BVUekkEwxtxskf33KfCD8rjwp0It7wvJtPtlaAQggDR6i dp0BfFsPVi6jDxUCNoxOLNl1AEYrmCYEjfdAGMR6NwZz+Zcu8U8eJnjlkGZuDi6zoZYi OcunwcUFSkZHlKu45PE5vgYhoVEqN8jqD4a6PNrVjw5+mDcz77tQJgoh+xOuYmttQyck W9HmU+W1UhbZQQP/6M6+wYzfzEXAp8Wn7wwFXjFtY2bW+DEcpIo0yd7KUUHka2zlHtoN YEmA== X-Gm-Message-State: AAQBX9fV4/IreyXYI8GZfRVM/+WRlED8bzTWS/P+VyGs0RLJG/m03feu IdztcpDHKSfjArAaJVrkszDdEHfhll9gQgkCl8Qs46IY X-Google-Smtp-Source: AKy350bzNFNHpRXyQZf2QKLUT8ffxNO8qrg/pTchahTlz95Zs0QySc6knejZ9Z/or1Ce2oVpBZS8zA== X-Received: by 2002:a62:1d53:0:b0:637:253a:531c with SMTP id d80-20020a621d53000000b00637253a531cmr5199258pfd.27.1681168091540; Mon, 10 Apr 2023 16:08:11 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id j16-20020a62e910000000b006258dd63a3fsm8333112pfh.56.2023.04.10.16.08.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Apr 2023 16:08:11 -0700 (PDT) Date: Mon, 10 Apr 2023 16:08:09 -0700 From: Stephen Hemminger To: Dinesh Kumar Cc: users@dpdk.org Subject: Re: How to use --vdev Options for ./dpdk-l3fwd? Message-ID: <20230410160809.11e6747f@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 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 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=input.pcap,tx_pcap=output.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 = 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=X,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) 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