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 C39DFA0032 for ; Wed, 13 Jul 2022 08:52:34 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 567B34282D; Wed, 13 Jul 2022 08:52:34 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id B92104282B for ; Wed, 13 Jul 2022 08:52:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657695152; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uBQH92J28coKQdXicBFRGjtENSru3h5LxHHlDuT2N/Y=; b=Fgaw7J/bLxbAua8+q+7QnOx3Szt4vHXInpLl7UHpVVhU0AYYO50ISMuSvrMCMOlR+pgFgD ZIPM3svFUebPKq+e190iFgwopNRmujSTFkDol4+wS3s/I2g3/RMHxzlq1S4VlkosOi9gw/ 2wI7AF+l5LN0LidzI5SF1pnsgYQUPDo= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-389-yUex2ZfBOdOC-7VJjNPMOg-1; Wed, 13 Jul 2022 02:52:30 -0400 X-MC-Unique: yUex2ZfBOdOC-7VJjNPMOg-1 Received: by mail-lj1-f198.google.com with SMTP id z23-20020a2e9b97000000b0025d7496a2f2so1145168lji.15 for ; Tue, 12 Jul 2022 23:52:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uBQH92J28coKQdXicBFRGjtENSru3h5LxHHlDuT2N/Y=; b=JAdarinI236K+uPBFHEGPlisqPHgB8VFbHRAvYJTsLEg6iobNvwEtjLDasibAPNBk3 BoaXaa8CDDyHTEx3U/0zF2EHTnN4Ct1vdk8eLZvmR1j0/rTXp2UyNWQ5nYJeYIheIrRr O+2KY8Uw5milurhUqUDVui5XsgAeu/NBVzytGwZ/FCSwhcVPiijPSDIbuSYIXd+iWDwT eA2YKKD+VrfhaWsQlxAkz+HYiUVDDCwQ3jEMzbnlRbxqEwGL5ii4MNOmtV+fPMfpNCSQ pEvo2YsSHmUQg+f/gUe37Cu/dATa9t1GATchm0bXGjnawusTWO0UaRd7I9zvKH8NAcfQ qdBQ== X-Gm-Message-State: AJIora8YdkPFsqptF+8e/SanOHPaSaOxjMn4BYWUXm1ZoUBQVgzeX51a Z9oFLCZxdf4I8E69F5d14l3QHVvvSDjEPQGM+PVo4mxtQXxJkIz449Fv/+Aw4nl7iIyNnasEtyA DuvsmX2OQl6OHRV9VId4wbg== X-Received: by 2002:ac2:593c:0:b0:489:cd83:86de with SMTP id v28-20020ac2593c000000b00489cd8386demr1183256lfi.553.1657695149222; Tue, 12 Jul 2022 23:52:29 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tB2LU2Ly8J54mz4OsfjVXOuVnchB7g7mmlaMxGCUmagCoa3piNdkal6W7pyPkQjboD9aCob5rRcQpFtABIIEE= X-Received: by 2002:ac2:593c:0:b0:489:cd83:86de with SMTP id v28-20020ac2593c000000b00489cd8386demr1183240lfi.553.1657695148986; Tue, 12 Jul 2022 23:52:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 13 Jul 2022 08:52:18 +0200 Message-ID: Subject: Re: skeleton code failing To: Lokesh Chakka Cc: users Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" 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, Jul 13, 2022 at 7:35 AM Lokesh Chakka wrote: > Would like to understand if I am missing something. I am new to this platform. > rte_eth_dev_count_avail is returning zero. > OS is Ubuntu 22.04. DPDK is latest version. > Cards are being detected by Linux. Ifconfig is showing the cards up. LED is also glowing. Indeed, DPDK provides a userspace driver for some NetXtreme nics (which is net/bnxt). This userspace driver does not rely on the bnxt Linux kernel driver. IOW, this card being detecting and working with the Linux kernel does not automatically mean that this nic can work with DPDK. We need more info on your nic, first. Can you share the pci id of this nic (like running lspci -n -s $pci_address)? It should be a 14e4:XXXX. Then you can check this XXXX against what your dpdk application supports. If it is a statically linked application, you can run: $ dpdk-pmdinfo.py /path/to/your/application Else, if your application is dynamically linked against DPDK driver, you can run this command against the net/bnxt driver .so.22 (for 21.11 and later releases): $ dpdk-pmdinfo.py /path/to/your/dpdk/drivers/librte_net_bnxt.so.22 You should get a list of supported NetXtreme nics, like: [snipped some other drivers compiled in my application] PMD NAME: net_bnxt PMD HW SUPPORT: Broadcom Inc. and subsidiaries (14e4) : BCM5745X NetXtreme-E RDMA Virtual Function (1606) (All Subdevices) Broadcom Inc. and subsidiaries (14e4) : BCM5745X NetXtreme-E Ethernet Virtual Function (1609) (All Subdevices) Broadcom Inc. and subsidiaries (14e4) : BCM57454 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb Ethernet (1614) (All Subdevices) Broadcom Inc. and subsidiaries (14e4) : NetXtreme-E RDMA Virtual Function (16c1) (All Subdevices) Broadcom Inc. and subsidiaries (14e4) : NetXtreme-C Ethernet Virtual Function (16cb) (All Subdevices) [snipped the rest] I hope you can find a (XXXX) corresponding to your NIC. -- David Marchand