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 BAB54A00C5 for ; Thu, 1 Dec 2022 17:50:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4E9FB42D11; Thu, 1 Dec 2022 17:50:06 +0100 (CET) Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) by mails.dpdk.org (Postfix) with ESMTP id 7A23342D0D for ; Thu, 1 Dec 2022 17:50:05 +0100 (CET) Received: by mail-pl1-f180.google.com with SMTP id p24so2198271plw.1 for ; Thu, 01 Dec 2022 08:50:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; 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=W1DP61YByp9AE635z2zHdsw8WxUxORrH3CKjQvCxmpE=; b=D+KJhP8pgjWekUTAdK+MbPuAhL4V+bTmTVBJQzUygT9rEgkWJZBKwbFO08mtVhEAut QO+aWkg4R3r3E8AOgjXi0WM1afbKjDuEJmstsP9Ckdztp7ME2A4aXtdwoZ2ESAax6wND rvrz4d4KmUzcW0Y4TIQ/flaAJy2AHMZrpYIpvpXi7wLovBRCesOfrKbizk2YlcSnd8b2 6Wb/gpye1rFVy7F0Jai4lp8ybk+je/j3VWe6Fk0MC+lWbzU4OLf7PokjnnFi4flWupSS X5f0OJqdp4QfmIX8fF8stvKi5t+7Wl8EkeUboQw2JNRSHmOMa7wFSFgLuT8Q2SyhB98W 99cQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=W1DP61YByp9AE635z2zHdsw8WxUxORrH3CKjQvCxmpE=; b=drvJqkhBbT1On/aTMeGUVF1gALYFUvYNzQfc4jhG1C4nOGEo4ecs8RVcxmlGvYCkpc exe/fYrA3zmRIUXi/0NwuuEkhWyO9ImuM5CjzqURxcfG/8wdXGaUc7AJC9PBJKxI6er2 e2y1+l8BrBNlilUCaCKcMiGcJ8knOcI59eMSqBiAvNuCSpMEXRk1O6CYUNgD36CoB/0N feU82oU53f5snyMVzM63g1OIv1kdsgEehY6Fz7QQA0MbQqiU7BGqBIyZjuflimcOR+f0 tUEnF6WBG+HYHqDHydiwlOP7I9p+cWxPHO+qjy633aeW+xd0Q9KHISSolewzzfgM2Fhh UitQ== X-Gm-Message-State: ANoB5plZ5YE4YGiorPMFNm+/Tju+hb39UHvi4wqG5vJeb+OOcPGLYL0T Ne5IdQYEauZRZlm48FpGkU/ctg== X-Google-Smtp-Source: AA0mqf6lQBEqJzkcMDQfeIyK3lif2winhiWdRciaPrWfbtTTKL86moAJ/kLlCpCbv+FLqjXhxqVgag== X-Received: by 2002:a17:90a:4a8f:b0:215:f80c:18e6 with SMTP id f15-20020a17090a4a8f00b00215f80c18e6mr78020581pjh.45.1669913404487; Thu, 01 Dec 2022 08:50:04 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id h14-20020a170902680e00b00186ffe62502sm3836539plk.254.2022.12.01.08.50.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Dec 2022 08:50:04 -0800 (PST) Date: Thu, 1 Dec 2022 08:50:02 -0800 From: Stephen Hemminger To: "Kyle.Gagnon@gd-ms.com" Cc: "users@dpdk.org" , Kyle Gagnon Subject: Re: DPDK Non-Supported Hardware Usage Question - Kyle Gagnon GDMS Message-ID: <20221201085002.742b6098@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 Wed, 30 Nov 2022 13:35:26 +0000 "Kyle.Gagnon@gd-ms.com" wrote: > Hello! > > My name is Kyle Gagnon and I work at General Dynamics Mission Systems. We are evaluating DPDK and its use. I am currently trying to get DPDK to work on a Xilinx ZCU102 evaluation board. The problem is that the NIC is an onboard ethernet interface so it does not go through any PCI. I won't be able to use an external NIC card so I have to work with what I have. I understand that I can use the PCAP library PMD. Here is my question if you don't mind helping me out! That will be really slow and limiting. Why use DPDK if there is no native driver support? > > I am compiling DPDK through meson and then in a custom application I am writing myself I have to use Makefiles. I need to statically link all of the libraries. So I did that and wrote an extremely basic program that doesn't do much at all. Here it is (I am copying from another computer. This is a C++ application and I am building it for ARM on an x86_64 Ubuntu WSL machine) > > DpdkEntry.cpp > > #include > #include > > #include > #include > #include > #include > #include > > Int main(int argc, char **argv) { > > int returnVal; > > std::cout << "Setting up EAL environment\n"; > > returnVal = rte_eal_init(argc, argv); > if (returnVal < 0) { > rte_exit(EXIT_FAILURE, "Error with initializing EAL\n"); > } > > rte_eal_cleanup(); > > return 0; > } > > When I run this application through a QEMU emulation of the ZCU102 board I use the following command > > dpdk-test -l 0-3 -n 4 -vdev 'net_pcap0,iface=eth0' > > I have built librte_net_pcap and linked it in so it is in the application. When I run the above command (using the above source code) I get the following: > > EAL: Detected CPU lcores: 4 > EALL Detected NUMA nodes: 1 > EAL: Detected static linkage of DPDK > EAL: failed to parse device "net_pcap0" > EAL: Unable to parse device 'net_pcap0,iface=eth0' > EAL: Error - exiting with code: 1 > Cause: Error with initializing EAL > > When I run a testpmd with the same parameters on the same emulated board I am able to use the ethernet port so what am I doing wrong with my custom code? I am going to forward this to my personal email in case I need to follow up with more information (the source code and building is on my personal computer rather than my work computer). Try adding printfs inside the pcap poll mode driver. It may not be getting loaded.